Skip to content

Conversation

@roshankumar0036singh
Copy link

Summary

Implements centralized logging configuration to eliminate useless INFO/DEBUG logs from CLI commands while maintaining full debugging capability.

Changes

  • New: [logging_config.py] Centralized logging with context-aware defaults
  • Updated: CLI commands now use WARNING level by default (clean output)
  • Updated: MCP server uses INFO level (operational visibility)
  • Updated: Database connection logs changed from INFO to DEBUG
  • Updated: FalkorDB worker startup messages reduced to DEBUG
  • Improved: Windows error messages guide users to Neo4j/WSL instead of unsupported FalkorDB

Verification

Screenshot 2026-01-02 153740

Features

  • Clean CLI output by default
  • Debug mode via CGC_LOG_LEVEL=DEBUG environment variable
  • Improved Windows support messaging

Testing

  • cgc stats - Clean output
  • cgc list - Clean output
  • cgc doctor - Clean output with improved Windows guidance
  • CGC_LOG_LEVEL=DEBUG cgc stats - Debug logs visible when needed

Closes #445

- Add logging_config.py with context-aware log levels (CLI=WARNING, MCP=INFO)
- Support CGC_LOG_LEVEL environment variable for debugging
- Update main.py to use quiet logging for CLI commands
- Change database connection logs from INFO to DEBUG level
- Update falkor_worker.py to reduce startup verbosity
- Simplify debug_log.py by removing custom log_mode toggle
- Improve Windows error messaging in doctor command

This ensures CLI commands produce clean output by default while
maintaining full debugging capability via CGC_LOG_LEVEL=DEBUG.
@vercel
Copy link

vercel bot commented Jan 2, 2026

@roshankumar0036singh is attempting to deploy a commit to the shashankss1205's projects Team on Vercel.

A member of the Team first needs to authorize it.

@roshankumar0036singh
Copy link
Author

@Shashankss1205 please review it

@Shashankss1205
Copy link
Owner

It doesnt work as intended!
image
Can you confirm from your end?

@roshankumar0036singh
Copy link
Author

roshankumar0036singh commented Jan 2, 2026

image there was small issue i overlooked as i was using the db through docker i didnt encountered these logs i will make a commit in it and you can check it afterwards @Shashankss1205

@roshankumar0036singh
Copy link
Author

check it now @Shashankss1205

@Shashankss1205
Copy link
Owner

image I still see many logs, can you tell me the reason for the same?

@roshankumar0036singh
Copy link
Author

roshankumar0036singh commented Jan 2, 2026

@Shashankss1205 bro check it the command might be using old code bcz i am using the same command and getting the output without any logs

@roshankumar0036singh
Copy link
Author

roshankumar0036singh commented Jan 2, 2026

see bcz mine is working perfectly
image
Did you pull the latest changes from my branch ? if yes then run pip install . and then verify once more @Shashankss1205

@roshankumar0036singh
Copy link
Author

@Shashankss1205 did the issue fixed or its still showing logging commands

@Shashankss1205
Copy link
Owner

This complete strategy will fail the end-2-end tests as you can see from the above Logs. But since you wasted a lot of time here, Let me do something to accept parts of it.

@roshankumar0036singh
Copy link
Author

@Shashankss1205 plz check now i have fixed the missing debug logger issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stop showing useless INFO logs when running cli commands

2 participants