Container Log Archive script should log to file as well as console
Bug #1888336 reported by
Thomas Cuthbert
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Container Log Archive Charm |
Fix Released
|
Undecided
|
Thomas Cuthbert |
Bug Description
Currently c-l-a only logs to console which is handy for debugging active issues, however it would be useful if it also logged to file so that we could review transient issues when they arise.
Related branches
~tcuthbert/container-log-archive-charm:master
- Stuart Bishop (community): Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 192 lines (+45/-17)7 files modifiedfiles/archive-to-azure.py (+2/-4)
files/archive-to-gce.py (+2/-4)
files/archive-to-s3.py (+2/-4)
files/archive-to-swift.py (+2/-4)
files/archive.py (+12/-1)
files/container-log-archive.logrotate (+12/-0)
hooks/hooks.py (+13/-0)
Changed in container-log-archive-charm: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I've seen on a host with this deployed where the .status file wasn't being updated and nagios alert firing. unfortunately, I ran the job manually which seems to have cleared this, and didn't get to look into it further when it happened.
Will need to keep digging and figure out why.