-
Notifications
You must be signed in to change notification settings - Fork 148
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
Unify the logging format when debugging is enabled #118
Labels
Comments
kzys
pushed a commit
to kzys/runtime
that referenced
this issue
Dec 17, 2022
Forward agent containerd events to shim and monitor task exits via event subscriptions
The runtime with an injectable Logger is for constructing a client. On the server side, logging is scattered among different components so it's more difficult. |
fredbi
added a commit
to fredbi/runtime
that referenced
this issue
Dec 13, 2023
This PR allows to set a logger in Context and DefaultRouter. * fixes go-openapi#118 Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
fredbi
added a commit
to fredbi/runtime
that referenced
this issue
Dec 14, 2023
* relinted debugLog as debugLogf * fixes go-openapi#244 (use logger.Debugf rather than logger.Printf) * fixes go-openapi#118 (added support for injectable logger in Context and DefaultRouter) * removed global debug logger Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we enable the debug mode, it uses the logging format defined in the standardLogger (https://github.com/go-openapi/runtime/blob/master/middleware/context.go#L35). It'd be great to reuse the Logger defined when configuring the runtime.
Is it possible to unify the logger format when debug is enabled? Or I am missing something
The text was updated successfully, but these errors were encountered: