-
Notifications
You must be signed in to change notification settings - Fork 206
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
Clean up logging / tracing logger output #5222
Labels
Comments
We should consistently use structured logging. |
1 task
Scaling ConsiderationsEach Meanwhile, having them turned on provides a certain form of observability. |
cannot save non-durableThese are all expected. ref f7c72f8
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What is the Problem Being Solved?
While developing for MN-1 we've accumulated a lot of log output. We won't want all of that in production.
Description of the Design
We can't simply condition on a prod vs dev environment variable because SES locks down.
We'll have to be judicious in what we log at all and have practices for enabling logging in dev that can't impact prod. For longer term solution see #1318
Security Considerations
Log output can provide information for attacks.
Test Plan
Look at log output in dev net.
The text was updated successfully, but these errors were encountered: