New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use 1 logging mechanism #14

Open

jmjatlanta opened this issue Jun 18, 2021 · 0 comments

Owner

jmjatlanta commented Jun 18, 2021

Komodo core uses several ways to log messages. Standardization is necessary.

Must:

Be set up early on (i.e. after command line and configuration file processing)
Send messages to a variety of places (i.e. syslog, console, log file), controllable from command line / config file
Is module-specific log settings a requirement (i.e. Log4j)? My opinion: rarely used in the real world beyond development phase.
Be configurable at runtime
Debug messages disabled in release mode
Be callable from C

Coding Guidelines:

Define what is fatal, error, warning, info, and debug
Discourage debug messages in code reviews
Disallow messages in production that contain complicated logic

Idea: A singleton (yes I know, yuck, or a global, or...) that does the right thing.

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