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
chore: Adding logging for datasource/save requests #14476
chore: Adding logging for datasource/save requests #14476
Conversation
I just checked the logs and looks like mysql will truncate at |
Codecov Report
@@ Coverage Diff @@
## master #14476 +/- ##
==========================================
+ Coverage 76.91% 76.95% +0.03%
==========================================
Files 955 955
Lines 48057 48108 +51
Branches 6034 6034
==========================================
+ Hits 36965 37023 +58
+ Misses 10894 10887 -7
Partials 198 198
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
lgtm
Co-authored-by: michelle_thomas <michelle.thomas@airbnb.com>
Co-authored-by: michelle_thomas <michelle.thomas@airbnb.com>
Co-authored-by: michelle_thomas <michelle.thomas@airbnb.com>
SUMMARY
I'd like to log requests to the /datasource/save endpoint so that we know when users alter a datasource.
(Edit: I was previously concerned about logging large data blobs in the json field but the size of this seems in line with other large payloads we are logging like /save_dash, the database like mysql will truncate large blobs). The data that automatically gets logged in the
json
column can be large (it includes all of the data for the datasource that is getting saved so if the datasource has a lot of columns they will all get logged).TEST PLAN
Edited a datasource from the
/tablemodelview/list/
and explore pages, confirmed logs in the logs table.ADDITIONAL INFORMATION
@john-bodley @etr2460