Chore: Moving to slog (folders) #87000
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zserge
requested review from
owensmallwood and
papagian
and removed request for
a team
zserge
added
no-backport
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This starts the migration of Grafana logging to stdlib's
log/slogAPI.Now instead of using
pkg/infra/logone can rely onslog.Default()logger and its derivatives.To make a logger with a custom logger name one should use
slog.Default().With("logger", "mylogger").For testing there is a no-op handler (logs produce no output) and a
t.Log()wrapper (logs produce normal test output).It's also possible to inject an
slog.Handler()with Wire to build more customised loggers on top of it.Following these practices would reduce the usage of pkg/infra/log a lot and would help with further modularisation of Grafana backend.