-
Notifications
You must be signed in to change notification settings - Fork 88
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
dev/next: log router output #2308
Conversation
✅ Docs Preview ReadyNo new or changed pages found. |
match level { | ||
"INFO" => tracing::info!(%message), | ||
"DEBUG" => tracing::debug!(%message), | ||
"TRACE" => tracing::trace!(%message), | ||
"WARN" => write!(f, "{} {}", warn_prefix, &message)?, | ||
"ERROR" => write!(f, "{} {}", error_prefix, &message)?, | ||
"UNKNOWN" => write!(f, "{} {}", unknown_prefix, &message)?, | ||
_ => {} |
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.
I feel like there's some sort of due diligence I could suggest to make sure the level we're setting is right (based on what's in the router, which I've sure you've looked at), but it's sort of escaping me right now; the only thing that sort of worries me is the catch-all at the bottom not emitting anything (but maybe it's better to emit nothing than to emit a bunch of "warning! no level set!" or whatever)
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.
Even though this is the same as the original implementation
Maybe this should be _ => write!(f, "{} {}", unknown_prefix, &message)?
?
whoa, this got weird after having new commits merged; going to leave the approval, but not totally sure about all the new stuff (going to assume it's alright, but re-request a review if you want a sanity check) |
a92a652
to
08b1bbb
Compare
Similar to the legacy implementation, this PR logs output from the running
router
binary.