You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: