Commit 1e38dd55 authored by Stephane Nicoll's avatar Stephane Nicoll

Merge branch '2.2.x'

Closes gh-19461
parents 065fe999 b268b573
...@@ -1634,7 +1634,7 @@ The following table shows how the `logging.*` properties can be used together: ...@@ -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.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment