Fix unnecessary meta_data being logged during breadcrumb validation #530
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
… during breadcrumb validation
tobyhs
reviewed
Jan 22, 2019
lib/bugsnag/breadcrumbs/validator.rb
Outdated
| @@ -26,21 +26,21 @@ def validate(breadcrumb) | |||
| if valid_meta_data_type?(v) | |||
| true | |||
| else | |||
| @configuration.warn("Breadcrumb #{breadcrumb.name} meta_data #{k}:#{v} has been dropped for having an invalid data type") | |||
| @configuration.debug("Breadcrumb #{breadcrumb.name} meta_data #{k} has been dropped for having an invalid data type") | |||
There was a problem hiding this comment.
Should you include v.class in the log message? (as that shouldn't be sensitive)
tobyhs
approved these changes
Jan 22, 2019
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.
Goal
Alters breadcrumb validation logs:
debugIn addition:
keyparameter from cache breadcrumbs due to potentially being an un-breadcrumbable typeFixes #528