root
/
spring-boot
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

Merge branch '2.2.x'

Browse Source 
Closes gh-19461
pull/19476/head
Stephane Nicoll 5 years ago
parent 065fe9996d b268b57339
commit 1e38dd5531
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
Unescape Escape View File

@ -1634,7 +1634,7 @@ The following table shows how the `logging.*` properties can be used together:
Log files rotate when they reach 10 MB and, as with console output, `ERROR`-level, `WARN`-level, and `INFO`-level messages are logged by default. Log files rotate when they reach 10 MB and, as with console output, `ERROR`-level, `WARN`-level, and `INFO`-level messages are logged by default.
Size limits can be changed using the configprop:logging.file.max-size[] property. Size limits can be changed using the configprop:logging.file.max-size[] property.
Previously rotated files are archived indefinitely unless the configprop:logging.file.max-history[] property has been set. Rotated log files of the last 7 days are kept by default unless the configprop:logging.file.max-history[] property has been set.
The total size of log archives can be capped using configprop:logging.file.total-size-cap[]. The total size of log archives can be capped using configprop:logging.file.total-size-cap[].
When the total size of log archives exceeds that threshold, backups will be deleted. When the total size of log archives exceeds that threshold, backups will be deleted.
To force log archive cleanup on application startup, use the configprop:logging.file.clean-history-on-start[] property. To force log archive cleanup on application startup, use the configprop:logging.file.clean-history-on-start[] property.

Write Preview
Loading…
Cancel
Save