feat: logging control through MCP_REDIS_LOG_LEVEL env var #58
+302
−30
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.
Logging is now controlled via an environment variable
MCP_REDIS_LOG_LEVEL
Use
MCP_REDIS_LOG_LEVEL
to set verbosityAccepted:
DEBUG, INFO, WARNING, ERROR, CRITICAL, NOTSET
Aliases:
WARN
→WARNING
,FATAL
→CRITICAL
Numeric values allowed (e.g., 10, +20)
Default (unset/unrecognized): WARNING
Handler behavior
If handlers already exist (uv/VS Code/pytest), we don’t add any. We only lower too‑strict handler levels so user's chosen level passes; we never raise them.
If no handlers exist, we add one
stderr
StreamHandler
with a simple format.Behavior changes
Default is quiet (WARNING+). Set
MCP_REDIS_LOG_LEVEL
to INFO/DEBUG to see more.Host-provided handlers are respected; we don’t add duplicates.
Before (noisy stderr tags)
After (default: WARNING)
Testing
Unit tests added for logging_utils. Full suite passing. Total coverage: 87.67%