-
Notifications
You must be signed in to change notification settings - Fork 229
Emit warning-level logs to syslog when log directory is unset #387
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
No code changes, just relocating the module in preparation for the next commit. Signed-off-by: James Bornholt <[email protected]>
Signed-off-by: James Bornholt <[email protected]>
|
Plan to finish review here tomorrow morning. Needed to learn a bit about |
Signed-off-by: James Bornholt <[email protected]>
Signed-off-by: James Bornholt <[email protected]>
dannycjones
left a comment
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.
Thanks James, this looks great and I'm glad to have this as the default if logging is not configured. The additional comments in the last commit also helped a lot.
The main concern I have is that it will become a file that most will not want to touch, so I'd like to make it as accessible as possible. The comments are along these lines.
Signed-off-by: James Bornholt <[email protected]>
dannycjones
left a comment
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.
LGTM!
Thanks for the updated comments, very clear.
Description of change
We disabled logging to a file by default in #373. But we'd still like to have a default home for high-severity messages, which is exactly what syslog is for.
This PR is the bare minimum to get
tracing-style structured logging into syslog. I hardcoded the verbosity towarn,awscrt=offand didn't think too hard about configuration: the syslog logger is on whenever the--log-directoryflag isn't set. Because I didn't think too hard about it, I also didn't update docs/LOGGING.md yet.This PR is two commits:
main.rsto its own file, just because it was getting big. No other code changes here.logging.rs.Does this change impact existing behavior?
No.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).