Skip to content
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.

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

Re-evaluate log levels #274

Open
ian-noaa opened this issue Dec 13, 2023 · 1 comment
Open

Re-evaluate log levels #274

ian-noaa opened this issue Dec 13, 2023 · 1 comment
Assignees
Labels
task Tasks break a project down into discrete steps

Comments

@ian-noaa
Copy link
Contributor

Our logs are fairly verbose, re-evaluate which log levels to use for which messages. Our logger has the following levels available (also below) and currently logs at the INFO level unless an env variable is set to log DEBUG messages.

We should probably demote a good number of log messages from Info to Debug.

Level Description
logging.DEBUG Detailed information, typically only of interest to a developer trying to diagnose a problem.
logging.INFO Confirmation that things are working as expected.
logging.WARNING An indication that something unexpected happened, or that a problem might occur in the near future (e.g. ‘disk space low’). The software is still working as expected.
logging.ERROR Due to a more serious problem, the software has not been able to perform some function.
logging.CRITICAL A serious error, indicating that the program itself may be unable to continue running.
@ian-noaa ian-noaa added the task Tasks break a project down into discrete steps label Dec 13, 2023
@ian-noaa ian-noaa self-assigned this Dec 13, 2023
Copy link

This issue is stale because it has been open 90 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task Tasks break a project down into discrete steps
Projects
None yet
Development

No branches or pull requests

2 participants