chore(reports): Improving logging around failed scheduled reports #19924
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
dpgaspar
approved these changes
May 3, 2022
sadpandajoe
pushed a commit
to preset-io/superset
that referenced
this pull request
May 3, 2022
(cherry picked from commit e1f53f2)
|
🏷️ preset:2022.17 |
hughhhh
pushed a commit
to hve-labs/superset
that referenced
this pull request
May 11, 2022
philipher29
pushed a commit
to ValtechMobility/superset
that referenced
this pull request
Jun 9, 2022
mistercrunch
added
🏷️ bot
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.
SUMMARY
Improving logging around scheduled reports. In the event that an unknown failure occurs, the current behavior is to log an
infowith only the description of the associated exception. This PR updates this logic to include a stack trace for better triage.