reporter/reporter.go: experiment: allow reporter to send the reported Level to Sentry #19
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.
What does this PR do?
After adding mechanisms to group handle the error level for given events based on the properties of their errors, the next step is to allow the developer to select the level to which a specific error is reported.
This will also allow us to easily keep reporting things as "warning" without cluttering Sentry in a needless way.
This patch needs to be accompanied by its corresponding patch on github.com/upfluence/log, for instance:
A pull request for this will be opened if/when this one is merged.
Fixes #
What are the observable changes?
Good PR checklist
Additional Notes