Investigate ease of plugins having own logging channel/level
Open
enhancement
Plugins
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 182
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
A plugin might want to control its own logging level (i.e. DEBUG or even TRACE instead of INFO, but only for it).
Investigate if we've made this easy, and if not, adjustments to make it so.
There's also the possibility that a plugin would want its own logging file, and we should make that easy as well.
Contributor guide
Research direction
Start by tracing how plugin logging is currently configured and whether a plugin can select its own logging level or output file. Compare the existing behavior with the requested DEBUG/TRACE levels and per-plugin files. Done means the investigation identifies the required adjustments and makes plugin-specific logging straightforward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100