We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
In addition to a convention for logger naming, the discussion in MatterMiners/tardis#137 and MatterMiners/tardis#146 suggests to add a convention for log levels as well.
Log Levels: We have the standard Python log levels. IMO these should be: CRITICAL: COBalD or TARDIS can't go on anymore and shuts down ERROR: Basically unused. WARNING: Recoverable errors. Dropped connections, timeouts, the like. Default for monitoring health when you know things generally work. INFO: High-level description of what goes on. Default for monitoring behaviour when you want to understand why things happen. DEBUG: Low-level/Implementation details. If things go wrong and you want to report them.
Log Levels: We have the standard Python log levels. IMO these should be:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In addition to a convention for logger naming, the discussion in MatterMiners/tardis#137 and MatterMiners/tardis#146 suggests to add a convention for log levels as well.
The text was updated successfully, but these errors were encountered: