feature: expose a model-level logging configuration for a unit of a charm
Bug #1861987 reported by
Dmitrii Shcherbakov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Currently there is no way for a charm to retrieve a model-level logging configuration for a particular unit.
The end goal is to be able to set up log levels for the root logger and a custom juju log handler such that log records are filtered at the framework level before they reach the controller if a human operator desires that.
The rationale is that log messages occupy storage space at the controller side and it may be useful to conserve it at the expense of losing some historical debugging information.
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.