将配置 Spring 命名空间的 xml 通过 Spring 启动，作业将自动加载。 表结构说明 事 件 追 踪 的 event_trace_rdb_url 属 性 对 应 库 自 动 创 建 JOB_EXECUTION_LOG 和 JOB_STATUS_TRACE_LOG 两张表以及若干索引。 JOB_EXECUTION_LOG 字段含义 字段名称 字段类型 是否必 填 描述 id VAR‐ failure_cause(如果作业执 行失败)。 6.1. 使用手册 49 Apache ShardingSphere ElasticJob document JOB_STATUS_TRACE_LOG 字段含义 JOB_STATUS_TRACE_LOG 记录作业状态变更痕迹表。可通过每次作业运行的 task_id 查询作业状态变化 的生命周期和运行轨迹。 6.1.4 操作 API ElasticJob 提供了 Root Config • � Job Types – � Simple – � Dataflow – � Script – � Http（3.0.0‐beta 提供） • � Event Trace – � Event Publisher – � Database Event Listener – ☐ Other Event Listener • ☐ Unified Schedule

Job Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Event Trace Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 6.2.7 Spring Namespace Focus business SDK, can work with Spring IOC • Admin Console – Job administration – Job event trace query – Registry center management 3 3 Environment Required 3.1 Java Java 8 or above required which is the value of the event tracing property event_trace_rdb_url will automati‐ cally create two tables JOB_EXECUTION_LOG and JOB_STATUS_TRACE_LOG and several indexes. 6.1. Usage 47 Apache ShardingSphere

rootLogger=ERROR, stdout # MyBatis logging configuration... log4j.logger.org.mybatis.example.BlogMapper=TRACE # Console output... log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout selectBlog=TRACE 与此相对，可以对一组mapper接口记录日志，只要对mapper接口所在的包开启日志功能即可： log4j.logger.org.mybatis.example=TRACE 某些查询可能会返回大量的数据，只想记录其执行的SQL语句该怎么办？为此，Mybatis中SQL语 句的日志级别被设为DEBUG（JDK Logging中为FINE），结果日志的级别为TRACE（JDK 对这个文件记录日志，只要对命名空间增加日志记录功能即可： log4j.logger.org.mybatis.example.BlogMapper=TRACE 进一步，要记录具体语句的日志可以这样做： log4j.logger.org.mybatis.example.BlogMapper.selectBlog=TRACE Web page converted to PDF with the PDFmyURL PDF creation

unintentionally initialized at build time. To see why com.sun.beans.introspect.ClassInfo got initialized use --trace-class- initialization=com.sun.beans.introspect.ClassInfo java.beans.Introspector was unintentionally unintentionally initialized at build time. To see why java.beans.Introspector got initialized use --trace-class-initialization=java. beans.Introspector com.sun.beans.util.Cache$Kind$2 was unintentionally initialized initialized at build time. To see why com.sun.beans.util.Cache$Kind$2 got initialized use --trace-class- initialization=com.sun.beans.util.Cache$Kind$2 com.sun.beans.TypeResolver was unintentionally initialized

unintentionally initialized at build time. To see why com.sun.beans.introspect.ClassInfo got initialized use --trace-class- initialization=com.sun.beans.introspect.ClassInfo java.beans.Introspector was unintentionally unintentionally initialized at build time. To see why java.beans.Introspector got initialized use --trace-class-initialization=java. beans.Introspector com.sun.beans.util.Cache$Kind$2 was unintentionally initialized initialized at build time. To see why com.sun.beans.util.Cache$Kind$2 got initialized use --trace-class- initialization=com.sun.beans.util.Cache$Kind$2 com.sun.beans.TypeResolver was unintentionally initialized

ShardingSphere supports Prometheus by default. • The tracing plugin is used to obtain the link trace information of SQL parsing and SQL execution. Apache ShardingSphere provides support for Jaeger,

ShardingSphere supports Prometheus by default. • The tracing plugin is used to obtain the link trace information of SQL parsing and SQL execution. Apache ShardingSphere provides support for Jaeger,

ShardingSphere supports Prometheus by default. • The tracing plugin is used to obtain the link trace information of SQL parsing and SQL execu‐ tion. Apache ShardingSphere provides support for exporting