指标记录每次申请内的http、es、mysql耗时，本篇探讨mysql局部
为什么说要摸索，这不是很简略的事么？然而能满足以下几点么？
- 能记录limit等参数
- 能将参数和sql写一起，能间接应用
- 能记录耗时
- 能计数累加,统计一次申请中sql执行的总数和总耗时
spring原生能力
logging.level.org.hibernate.SQL=debuglogging.level.org.hibernate.type.descriptor.sql.BasicBinder=trace通过下面两条配置。
- ✔️能够显示sql.
- ❌不能和参数一行显示
- ❌不能显示limit参数
- ❌不能计数和记录耗时
2021-02-23 19:35:42.932 DEBUG 97586 --- [ restartedMain] org.hibernate.SQL : select admin0_.id as id1_0_, admin0_.create_time as create_t2_0_, admin0_.modify_time as modify_t3_0_, admin0_.email as email4_0_, admin0_.password as password5_0_, admin0_.status as status6_0_, admin0_.username as username7_0_ from admin admin0_ where admin0_.username=?2021-02-23 19:35:42.949 TRACE 97586 --- [ restartedMain] o.h.type.descriptor.sql.BasicBinder : binding parameter [1] as [VARCHAR] - [root]原生log+org.hibernate.EmptyInterceptor
org.hibernate.EmptyInterceptor提供钩子，hibernate自身提供entity的curd钩子。重写EmptyInterceptor办法，能够实现计数。然而onPrepareStatement办法只是拆卸sql前的事件，而且不是残缺的sql。
- ✔️ 能够显示sql
- ❌ 不能和参数一行显示
- ❌ 不能显示limit参数
- ✔️ 能计数
- ❌ 不能记录耗时
spring.jpa.properties.hibernate.ejb.interceptor=com.vison.itdoc.config.HibernateInterceptorpublic class HibernateInterceptor extends EmptyInterceptor { @Override public boolean onLoad(Object entity, Serializable id, Object[] state, String[] propertyNames, Type[] types) {// Log.info("onload...", entity) return true; } @Override public String onPrepareStatement(String string) { // count++ return INSTANCE.onPrepareStatement(string); } @Override public void afterTransactionCompletion(Transaction t) { INSTANCE.afterTransactionCompletion(t); Log.info("after trans complete", t); } }log4jdbc
log4jdbc能很好的解决sql残缺显示和记录耗时的问题
2021-02-23 19:59:13.709 INFO 97586 --- [nio-8081-exec-1] jdbc.sqltiming : select posts0_.id as id1_2_, posts0_.create_time as create_t2_2_, posts0_.modify_time as modify_t3_2_, posts0_.content as content4_2_, posts0_.title as title5_2_ from posts posts0_ where 1=1 order by posts0_.id asc limit 10 ; {executed in 1 msec}还可能定义超过1定工夫的执行sql记录为error类型。
<dependency> <groupId>com.googlecode.log4jdbc</groupId> <artifactId>log4jdbc</artifactId> <version>1.2</version> <scope>runtime</scope> </dependency>spring.datasource.driver-class-name: net.sf.log4jdbc.DriverSpy#应用log4jdbc后mysql的urlspring.datasource.url=jdbc:log4jdbc:mysql://localhost:3306/xxxx?useUnicode=true&characterEncoding=UTF-8#应用log4jdbc后oracle的url#spring.datasource.url: jdbc:log4jdbc:oracle:thin:@127.0.0.1:1521:orcl留神须要增加spring.datasource.driver-class-name 和更改 spring.datasource.url 将jdbc改为 jdbc:log4jdbc
log4jdbc.properties能够定义更多配置
#配置为须要记录的包或类匹配门路#log4jdbc.debug.stack.prefix=com.drp#log4jdbc加载的drivers (驱动名)#log4jdbc.drivers=oracle.jdbc.OracleDriverlog4jdbc.auto.load.popular.drivers=true#在日志中显示warn正告log4jdbc.statement.warn=true#毫秒值.执行工夫超过该值的SQL语句将被记录为warn级别.log4jdbc.sqltiming.warn.threshold=2000#毫秒值.执行工夫超过该值的SQL语句将被记录为error级别.log4jdbc.sqltiming.error.threshold=3000#是把boolean记录为 'true'/'false' 还是 1/0. 默认设置为false,不启用,为了移植性.#log4jdbc.dump.booleanastruefalse=true#输入的sql,一行最大的字符数，默认90. 当前新版可能为0#log4jdbc.dump.sql.maxlinelength=90#如果在调试模式下转储，则转储整个堆栈跟踪 默认falselog4jdbc.dump.fulldebugstacktrace=false#是否记录某些类型的语句，默认truelog4jdbc.dump.sql.select=truelog4jdbc.dump.sql.insert=truelog4jdbc.dump.sql.delete=truelog4jdbc.dump.sql.update=truelog4jdbc.dump.sql.create=true#输入sql开端处退出分号，默认falselog4jdbc.dump.sql.addsemicolon=true#将此设置为false以不修剪已记录的SQLlog4jdbc.trim.sql=true#将此设置为false不删除额定的空行log4jdbc.trim.sql.extrablanklines=true#log4jdbc.suppress.generated.keys.exception=false- ✔️ 能够显示sql
- ✔️ 不能和参数一起显示
- ✔️ 不能显示limit参数
- ❌ 能计数
- ✔️ 能记录单个sql耗时
- ❌ 不能统计总耗时
有余的是，单纯log4jdbc并不能满足所有。实践上log4jdbc+org.hibernate.EmptyInterceptor能够满足需要了
P6Spy
测试结束，发现P6Spy目前最能满足需要：
- ✔️ 能够显示sql
- ✔️ 不能和参数一起显示
- ✔️ 不能显示limit参数
- ✔️ 能计数
- ✔️ 不能记录耗时
- ✔️ 反对curd事件前后钩子，钩子参数返回sql和执行耗时及异样信息????
<dependency> <groupId>p6spy</groupId> <artifactId>p6spy</artifactId> <version>3.9.1</version> </dependency>同log4jdbc须要改driver和url
spring.datasource.driver-class-name=com.p6spy.engine.spy.P6SpyDriverspring.datasource.url=jdbc:p6spy:mysql://localhost:3306/test?useLegacyDatetimeCode=false&serverTimezone=UTCpsy.properties能够定义更多配置
#modulelist=com.p6spy.engine.spy.P6SpyFactory,com.p6spy.engine.logging.P6LogFactory,com.p6spy.engine.outage.P6OutageFactorymodulelist=com.vison.itdoc.config.CustomeP6Factory,com.p6spy.engine.logging.P6LogFactory,com.p6spy.engine.outage.P6OutageFactory#moduelist很要害，我这里应用了自定义的Factory，因为我须要自定义eventappender=com.p6spy.engine.spy.appender.Slf4JLoggerlogMessageFormat=com.p6spy.engine.spy.appender.CustomLineFormatcustomLogMessageFormat=%(executionTime) ms|%(category)|%(sql)excludecategories=result,resultset,info,debug失常应用默认配置就能够显示出sql和耗时信息
4 ms|statement|select admin0_.id as id1_0_, admin0_.create_time as create_t2_0_, admin0_.modify_time as modify_t3_0_, admin0_.email as email4_0_, admin0_.password as password5_0_, admin0_.status as status6_0_, admin0_.username as username7_0_ from admin admin0_ where admin0_.username='root'能够看到，耗时信息和理论参数
自定义事件
modulelist=com.p6spy.engine.spy.P6SpyFactory改成自定义Factory
自定义Factory
public class CustomeP6Factory implements com.p6spy.engine.spy.P6Factory { @Override public P6LoadableOptions getOptions(P6OptionsRepository optionsRepository) { return new P6SpyOptions(optionsRepository); } @Override public JdbcEventListener getJdbcEventListener() { return new P6spyListener(); //应用自定义Listener }}自定义事件
public class P6spyListener extends JdbcEventListener { @Override public void onAfterExecuteQuery(PreparedStatementInformation statementInformation, long timeElapsedNanos, SQLException e) { App.sqlCount.incrementAndGet(); Log.info("execute query...", statementInformation.getSqlWithValues()); } @Override public void onAfterExecuteUpdate(PreparedStatementInformation statementInformation, long timeElapsedNanos, int rowCount, SQLException e) { App.sqlCount.incrementAndGet(); Log.info("execute update..", statementInformation.getSqlWithValues()); } @Override public void onAfterExecute(StatementInformation statementInformation, long timeElapsedNanos, String sql, SQLException e) { Log.info("execute..", statementInformation.getSqlWithValues()); }}能够看到，我在自定义事件中进行了sql计数.于是我能够在申请完结时打印每次申请的总sql执行次数。
public class RequestInitInterceptor implements HandlerInterceptor { public RequestInitInterceptor() { } @Override public boolean preHandle(HttpServletRequest request, HttpServletResponse response, Object handler) throws Exception { App._uniq_req_no = UUID.randomUUID().toString(); App.sqlCount = new AtomicInteger(0); Log.setMsgTraceNo(App._uniq_req_no); Log.info("request start...", handler); return true; } @Override public void afterCompletion(HttpServletRequest request, HttpServletResponse response, Object handler, Exception ex) throws Exception { Log.info(String.format("finish request sql执行次数:%s", App.sqlCount)); }}因为事件参数还给出了timeElapsedNanos,最终咱们还能统计出所有sql执行的耗时。这样一来咱们就能看出一次申请内，最耗时的操作具体是什么。达到相似以下成果：