-
Notifications
You must be signed in to change notification settings - Fork 885
feat: use named loggers in coderd
#8148
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's very possible the additional logger errors are failing tests, typically I believe slogtest fails the test if an error level is logged (unless explicitly ignored when creating slogger).
Other than that, looks fine 👍🏻. Suggestions are optional.
@@ -454,6 +454,10 @@ func (api *API) postWorkspacesByOrganization(rw http.ResponseWriter, r *http.Req | |||
}, nil) | |||
var bldErr wsbuilder.BuildError | |||
if xerrors.As(err, &bldErr) { | |||
if bldErr.Status == http.StatusInternalServerError { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am I the only one that reads this as "boulder"? 😂
Oh, you're right! I totally forgot about this. I assume that we have to disable this feature of slogtest. |
coderd
Related: #6726
This PR modifies logger configuration to use named loggers. The idea is to allow DevOps or admins to configure log alarms (catchphrases) for specific issues:
[erro]
coderd
workspace build error
[erro]
coderd.autobuild
workspace build error
[erro]
coderd.provisionerd-%s
[erro]
coderd.userauth
[erro]
coderd.prometheusmetrics