[ http://issues.apache.org/jira/browse/IBATIS-324?page=comments#action_12441190 ] Kjirsten Koka commented on IBATIS-324: --------------------------------------
>>>> and report by hour/date # of times a statment was used. >> >>That can be added outside of iBATIS. You can inject a proxy between the >>SqlMapClient interface and the default >>implementation to track these stats. >>If you build such a thing, we can consider adding it to the framework if >>others are >>interested. Recently I ran across JAMon 2.2 (jamonapi.sourceforge.net/) - it has a nifty jdbc driver proxy that can track SQL statements issued by your app, although you probably wouldn't be able to get the exact time a query was run as it aggregates the usage statistics. It is very useful for identifying long-running queries. It will definitely show you how many times a query has been [re-]used, as well as average, min, and max run times. regards, Kjirsten > cache hits/misses > ----------------- > > Key: IBATIS-324 > URL: http://issues.apache.org/jira/browse/IBATIS-324 > Project: iBatis for Java > Issue Type: New Feature > Components: SQL Maps > Reporter: V.C. > Priority: Minor > > It be nice to be able in real time and loged report on cache hits/misses > monitoring, size of cache by map name in megs, and report by hour/date # of > times a statment was used. > (also log the slow sql statements, like anything that takes more then 1/3 of > a seconds to log the statment and arguments). > these are standard managment issues that come up now and then. > i'd consider implementing if that helps. > .V -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
