Soften the logging #217
Merged
Soften the logging #217
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
apaleslimghost
approved these changes
Jul 11, 2023
One of the reasons we have a log level of `warn` is because we traditionally over-logged with a level of `info`. I'm switching some of the info-level logs in our dependencies to `debug` so that you can opt in when debugging an app but we don't flood Splunk.
rowanmanning
force-pushed
the
soften-the-logging
branch
from
1286f15
to
52434b5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One of the reasons we have a log level of
warnis because we traditionally over-logged with a level ofinfo. I'm switching some of the info-level logs in our dependencies todebugso that you can opt in when debugging an app but we don't flood Splunk.