Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
S
srm
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Jobs
Commits
Open sidebar
aship
srm
Commits
023f0cc2
Commit
023f0cc2
authored
Jul 26, 2019
by
顾俭
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
修改日志配置
parent
3f561f7a
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
34 deletions
+15
-34
logback-spring.xml
src/main/resources/logback-spring.xml
+15
-34
No files found.
src/main/resources/logback-spring.xml
View file @
023f0cc2
...
...
@@ -8,33 +8,30 @@
</appender>
<!-- 文件保存日志的相关配置 -->
<appender
name=
"
ERROR
-OUT"
class=
"ch.qos.logback.core.rolling.RollingFileAppender"
>
<file>
log/srm.log
</file>
<appender
name=
"
FILE
-OUT"
class=
"ch.qos.logback.core.rolling.RollingFileAppender"
>
<file>
${LOG_FILE:-.}1111
</file>
<encoder>
<pattern>
[ %-5level] [%date{yyyy-MM-dd HH:mm:ss.SSS}] [%thread] %logger{96} [%file:%line] - %msg%n
</pattern>
</encoder>
<!-- 循环政策:基于时间创建日志文件 -->
<rollingPolicy
class=
"ch.qos.logback.core.rolling.TimeBasedRollingPolicy"
>
<rollingPolicy
class=
"ch.qos.logback.core.rolling.
SizeAnd
TimeBasedRollingPolicy"
>
<fileNamePattern>
log/srm-%d{yyyy-MM-dd}.%i.log
</fileNamePattern>
<maxFileSize>
50 MB
</maxFileSize>
<!-- 最大保存时间:30 days-->
<maxHistory>
30
</maxHistory>
<totalSizeCap>
10GB
</totalSizeCap>
<timeBasedFileNamingAndTriggeringPolicy
class=
"ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"
>
<!--文件达到 最大50MB时会被压缩和切割 -->
<maxFileSize>
50 MB
</maxFileSize>
</timeBasedFileNamingAndTriggeringPolicy>
</rollingPolicy>
</appender>
<!-- 具体控制台或者文件对日志级别的处理还要看所在appender配置的filter,如果没有配置filter,则使用root配置 -->
<root
level=
"INFO"
>
<appender-ref
ref=
"STDOUT"
/>
<appender-ref
ref=
"
ERROR
-OUT"
/>
<appender-ref
ref=
"
FILE
-OUT"
/>
</root>
<!--
erp接口错误日志写入error-erp
.log-->
<appender
name=
"ERROR-
ERP
"
class=
"ch.qos.logback.core.rolling.RollingFileAppender"
>
<file>
log/error
-erp
.log
</file>
<!--
错误日志写入error
.log-->
<appender
name=
"ERROR-
OUT
"
class=
"ch.qos.logback.core.rolling.RollingFileAppender"
>
<file>
log/error.log
</file>
<encoder>
<pattern>
[ %-5level] [%date{yyyy-MM-dd HH:mm:ss.SSS}] [%thread] %logger{96} [%file:%line] - %msg%n
</pattern>
</encoder>
...
...
@@ -44,32 +41,16 @@
<maxHistory>
30
</maxHistory>
<totalSizeCap>
1GB
</totalSizeCap>
</rollingPolicy>
<filter
class=
"ch.qos.logback.classic.filter.LevelFilter"
>
<level>
ERROR
</level>
<onMatch>
ACCEPT
</onMatch>
<onMismatch>
DENY
</onMismatch>
</filter>
</appender>
<!--erp接口另加错误输出-->
<logger
name=
"com.i1.erp"
level=
"error"
>
<appender-ref
ref=
"ERROR-
ERP
"
/>
<appender-ref
ref=
"ERROR-
OUT
"
/>
</logger>
<!--以下可生效但已移到yml配置方便更改-->
<!--显示SQL JPA show-sql已经显示了 不然重复-->
<!--<logger name="org.hibernate.SQL" level="DEBUG" />-->
<!--参数值和返回值,TRACE级别,可以分开设-->
<!--<logger name="org.hibernate.type.descriptor.sql" level="TRACE"/>-->
<!--<logger name="org.hibernate.type.descriptor.sql.BasicBinder" level="TRACE"/>-->
<!--<logger name="org.hibernate.type.descriptor.sql.BasicExtractor" level="TRACE"/>-->
<!--profile配置-->
<!--<springProfile name="staging">-->
<!--<logger name="org.hibernate.type.descriptor.sql.BasicBinder" level="TRACE"/>-->
<!--<logger name="org.hibernate.type.descriptor.sql.BasicExtractor" level="TRACE"/>-->
<!--</springProfile>-->
<!--<springProfile name="prod">-->
<!--</springProfile>-->
<!--<springProfile name="gujian">-->
<!--<logger name="org.hibernate.type.descriptor.sql.BasicBinder" level="TRACE"/>-->
<!--<logger name="org.hibernate.type.descriptor.sql.BasicExtractor" level="TRACE"/>-->
<!--</springProfile>-->
</configuration>
\ No newline at end of file
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment