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

Switch to slog #476

Open
fabriziosestito opened this issue Feb 18, 2025 · 0 comments
Open

Switch to slog #476

fabriziosestito opened this issue Feb 18, 2025 · 0 comments

Comments

@fabriziosestito
Copy link
Contributor

fabriziosestito commented Feb 18, 2025

Currently, we use zerolog as our primary logger.
Switching to slog could be beneficial, as it offers structured logging and is included in the standard library, eliminating the need for external dependencies.

Additionally, we are using a global logger, which is considered an anti-pattern. A better approach would be to inject the logger into the Scanner and clients through dependency injection. This would allow us to use an attribute to include the component name in log entries.

Check that the PolicyReport logging outputs are the same (some users consume these logs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant