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

chore: Define logging levels #10116

Closed

spalladino opened this issue Nov 21, 2024 · 1 comment · Fixed by #10355

Assignees

Collaborator

spalladino commented Nov 21, 2024

Define the logging levels we want to use across the app. Consider extremely noisy components like the AVM.

spalladino self-assigned this

Collaborator Author

spalladino commented Nov 21, 2024 •

edited

Loading

I propose going with:

fatal: the process dies
error: an unexpected error happened
warn: we have strayed from the happy path
info: what an operator would want to see while running a process
verbose: what we want to see when testing a component
debug: what we need to troubleshoot an issue
trace: what we enable when we want to break the terminal

spalladino mentioned this issue

chore!: Remove debug and winston in favor of pino #10355

Merged

spalladino closed this as completed in #10355

spalladino closed this as completed in

c246aba

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