Add configurable logging levels via LOG_LEVEL environment variable #666
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add LOG_LEVEL environment variable support (DEBUG, INFO, WARNING, ERROR, CRITICAL) - Change default logging level from DEBUG to INFO to reduce noise - Configure root logger to ensure all loggers respect LOG_LEVEL setting - Update Docker configuration to support LOG_LEVEL - Update documentation to reflect new optional environment variable and available values
|
What an unfortunate PR number 😅 It's safe I tested it! Also I sound grumpy in the linked issue, I'm not! Thanks for all your efforts! Hope this helps/thanks for looking at it. |
|
This is great work. i'll test it out and try to implement. |
- Change verbose INFO messages to DEBUG for technical internals - Maintain user-friendly INFO messages for key actions and results - Update logger configuration for consistent formatting across modules - Apply uniform logging patterns to all app modules (sonarr, radarr, lidarr, readarr, whisparr) - Remove timezone labels from individual log lines for cleaner output This significantly reduces log noise while keeping important user-facing information visible. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
|
I've expanded this PR a bit to recategorize a bunch of internals from info to debug level also, along with removing the long-form timezone from the datestamp for file size and clarity. I also cleaned up a couple loggers that were using the default logging format instead of the custom Huntarr scheme. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds configurable logging levels to reduce log noise in container deployments.
Issue: #568
Changes
Testing
Python Syntax & Import Tests
settings_manager.py,logger.py) compile without syntax errorsget_log_level(),configure_root_logger()) are properly defined and callableLOG_LEVEL=DEBUG→ returns 10 (DEBUG level)Docker Integration Tests
ENV LOG_LEVEL=INFOproperly set as default in DockerfileLOG_LEVEL=${LOG_LEVEL:-INFO}works correctly in docker-compose.ymlLOG_LEVEL=INFOin container-e LOG_LEVEL=WARNINGproperly overrides to WARNINGEnvironment Variable Validation
Breaking Changes
None - fully backward compatible.