-
Notifications
You must be signed in to change notification settings - Fork 559
Implement proper Log Levels and support Structured Logging capabilities #1923
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
Comments
Hi @aldoborrero ! Thanks for creating this issue. You are right its on our todo list to add support for log levels and configurable formats, I'm super happy to accept contributions in this area so if you have a WIP or partial implementation of some statement that you would like to contribute we'd love to get those reviewed! Many thanks for considering contributing to our project! |
Hi @aldoborrero before I forget I'm not sure if we are able to accept contributions to the ee/ folder therefore if you could hold off on any changes to that codebase it would be appreciated since I might have to contribute themselves due to some legal implications |
How do I select log level using env vars? Any way to do that? Trying to debug something and the debug logs would be useful |
I've been working with the digger codebase recently and noticed that all log statements use
Println
rather than appropriate log levels. This approach can result in excessive logging output in some scenarios.Currently, the backend CLI doesn't provide options for:
Are there any plans to introduce more sophisticated logging solutions like zerolog or Go's built-in
slog
? This would allow for better log filtering and improved troubleshooting capabilities, especially in production environments.Happy to discuss this further or contribute to implementation if there's interest (I started working on it on a branch).
The text was updated successfully, but these errors were encountered: