🏗️ Architecture: How should we optimize the console-appender to reduce INFO l...

📋 Decision Context

Question:

How should we optimize the console-appender to reduce INFO log noise from LoggerService?

Task: Session 26.3 Final - Console Appender Optimization

🎯 Decision Made

Chosen:

Change MINIMUM_LOG_LEVEL from INFO to WARN in console-appender.ts to filter out INFO logs while preserving warnings and errors

Options Considered:

1. Change MINIMUM_LOG_LEVEL to WARN
2. Disable console-appender entirely
3. Add SOURCE_FILTERS for specific services
4. Keep INFO logs but reduce verbosity

💭 Reasoning

After migrating theme and icon services to createLogger, analysis showed the remaining ~60+ console logs were from console-appender.ts (the @libs-core/log-system ConsoleAppender) displaying INFO-level logs from services using LoggerService. Changed MINIMUM_LOG_LEVEL from LogLevel.INFO to LogLevel.WARN to filter out routine INFO logs while preserving essential WARNING and ERROR logs. This achieves ~90% total console noise reduction (from ~100+ logs to ~10 logs on page load). Services can still log INFO internally, but it won't clutter the console by default. Can be temporarily changed back to INFO when debugging specific issues. Also migrated LoadingOrchestratorService (2 console.log statements) to createLogger for consistency. Result: Clean, professional console by default with full debugging capability available through configuration.

📁 Files Involved

• libs/core/log-system/src/lib/appenders/console-appender.ts
• apps/gograb-space/src/app/services/loading-orchestrator.service.ts

🔗 Related

• Decision ID: dev_1767737591079_qi6lmz0
• Session: 22
• Workspace: editor2

Auto-generated by MCP Smart Consolidation