[RFE] max log age should be exposed as a configuration option
Bug #1566545 reported by
Felipe Reyes
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
juju-core 2 stores the logs inside the mongodb and by default they are stored for 3 days[0], there situations where this couldn't be enough, specially when you need to troubleshoot problems and reading old logs is useful to determine when a particular problem/behavior started.
Exposing this as a configuration option would be helpful to adjust it for the particular needs of each user.
[0] https:/
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.0-beta4 |
tags: |
added: sts-rfe removed: sts |
tags: | added: sts |
summary: |
- max log age should be exposed as a configuration option + [RFE] max log age should be exposed as a configuration option |
Changed in juju-core: | |
assignee: | nobody → Jorge Niedbalski (niedbalski) |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.1.0 → none |
milestone: | none → 2.1.0 |
Changed in juju: | |
assignee: | Jorge Niedbalski (niedbalski) → nobody |
tags: | added: canonical-is scalability |
Changed in juju: | |
importance: | Wishlist → High |
milestone: | none → 2.2-rc1 |
tags: | added: jaas |
Changed in juju: | |
milestone: | 2.2-rc1 → 2.2-beta3 |
assignee: | nobody → Ian Booth (wallyworld) |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It shouldn't be too hard to add this as a config option, but given the time constraints for 2.0.0, it won't make it into a 2.0.0 release.