[LOGTOOLS-30] Distinguish in-memory vs. webapp logger configs Created: 05/Oct/17  Updated: 24/Mar/22

Status: Open
Project: Magnolia Log Tools
Component/s: None
Affects Version/s: 1.1
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

Since the Log4j 2 upgrade, inherited loggers are no longer displayed in the log levels subapp.
We consequently removed the "inherited" column, and added an action for adding an "in-memory" logger config, to customize level for a specific logger.

I would suggest marking logger configs which are added "in memory" (with a status column), vs. those coming from webapp (XML) config;
plus maybe an option to remove an explicit in-memory logger config (to restore default inherited level).

We might as well add a level select to the new logger config form (currently level defaults to DEBUG for new entries).


Generated at Mon Feb 12 06:01:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.