Limit size of logs to 1GB by default (10 files × 100 MB), add ability to configure logging drivers. Fixes #762 #788
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now logs can not fill the entire disc, see initial issue. Limits are configurable. As bonus we’re now able even to change logging driver to
syslog
,fluentd
, or whatever.I have not updated readme, because not sure in my English. I’ll write about the new features here. I hope someone else will complement the readme on this basis.
Now possible to configure logging drivers via
log
object inmup.json
.Rotating logs
To set limits of logs to 5 files 200 MB each:
If you want single 1 GB file:
Send logs to third-party
Let’s send our logs to Logentries:
Note! Accesing logs via
mupx logs
command works only with default driver which isjson-file
.Options reference
All of the possible drivers and options can be found here: https://docs.docker.com/v1.8/reference/logging/overview/
Compatibility
This works via
--log-driver
and--log-opt
flags, which appeared in Docker v1.8. So deploy process can fail if you use an older Docker.