fieldju/logback-s3-rolling-policy — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2017-10-12
Automatically ship rotating application log files to an S3 bucket for centralized, searchable storage.
Organize uploaded logs in S3 by date or machine using custom folder structures and filename prefixes.
Run log rolling by file size or by time interval, depending on which policy you configure.
Ensure the current log file is uploaded to S3 before a Java app shuts down.
| fieldju/logback-s3-rolling-policy | 123satyajeet123/bitnet-server | alexbloch-ia/legal-data | |
|---|---|---|---|
| Stars | — | 0 | 0 |
| Language | Shell | Shell | Shell |
| Last pushed | 2017-10-12 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | moderate | easy | moderate |
| Complexity | 2/5 | 2/5 | 2/5 |
| Audience | developer | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Requires an AWS account and S3 bucket with appropriately scoped IAM credentials.
A Java logging add-on that automatically uploads your app's log files to Amazon S3 once they hit a size or time limit, so you get centralized log storage with no extra code.
Mainly Shell. The stack also includes Java, Logback, Amazon S3.
Dormant — no commits in 2+ years (last push 2017-10-12).
License terms are not stated in the explanation.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.