-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Report Normalization failures to Sentry #15695
Merged
Merged
Changes from all commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
145bae5
bulk
Phlair 68285d9
simplification
Phlair 70a4141
voila
Phlair eec2bd3
normalization version
Phlair 681d976
Merge branch 'master' into george/normalization-sentry
Phlair 3564c92
key prefix & pmd fix
Phlair 1e7f1ec
bits
Phlair 518c99a
Merge branch 'master' into george/normalization-sentry
Phlair d63189c
test fix
Phlair dea2aef
handle more dbt error structures and DRY
Phlair fe49c46
Merge branch 'master' into george/normalization-sentry
Phlair ec590da
format
Phlair a169a3b
better code comment
Phlair fd7654b
Merge branch 'master' into george/normalization-sentry
Phlair 7d4c0e7
enum for keys
Phlair 23d5471
Merge branch 'master' into george/normalization-sentry
Phlair 76fae3c
fix pmd
Phlair e21dc1d
Merge branch 'master' into george/normalization-sentry
Phlair f5ca8d7
I _love_ pmd
Phlair de453be
Merge branch 'master' into george/normalization-sentry
Phlair 0fa918e
Merge branch 'master' into george/normalization-sentry
Phlair e38e896
Merge branch 'master' into george/normalization-sentry
Phlair File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how common is it that the line immediately following
Database error
is the "interesting" one? e.g: is it 100% of the time based on a reasonable empirical sample size?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I was going for a classic 80-20 coverage move here, using the following data:
all normalization-system-errors (with the new failure reasons)
1,110 rows
Filtering for 'database errors'
736 rows
Nominal 736/1110 (66%)
Unique 368/442 (83%)
694/736 (~94%) follow the pattern of line immediately following "Database Error in model" is the single useful part.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did some futher investigation today looking deeper at the complete set of failures we've encountered (coming from those metabase links above) and decided it's not significant extra work to cover a lot of the possible error structures based on what we've seen so far:
The other 42 errors follow 1 of 3 patterns:
Currently implementing specific logic for these three extra edge cases so we cover all currently known database errors. (No doubt there are other edge cases that exist and we haven't encountered but we can build upon this parsing code over time.)
Also implementing logic for the rest of the error types (the other ~20% of unique errors we've seen):
Basing the logic from our dataset in Metabase (in previous comment links), now covering >95% of every dbt error we've seen since implementing normalization failure reasons.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes will also solve this point