We should connect redash to our production iodide database (the one powering iodide.telemetry.mozilla.org) so we can analyze various things about internal usage, for example: 1) Which notebooks have many edits 2) How many active notebooks we have 3) Most frequent users To start with I think we only need access to the following tables: `base_user` (note: exclude the password, is_superuser, is_staff fields) `notebooks_notebook` (I may rename this to just `notebook` soon) `notebooks_notebookrevision` (I may rename this to `notebook_revision` soon) This is similar to what we did with treeherder way back when in bug 1279580. I think this is slightly lower priority than getting the production server fully up and running, but it would be nice to have this shortly after.
Bug 1583342 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We should connect redash to our production iodide database (the one powering iodide.telemetry.mozilla.org) so we can analyze various things about internal usage, for example: 1) Which notebooks have many edits 2) How many active notebooks we have 3) Most frequent users To start with I think we only need access to the following tables: `base_user` (note: exclude the password, is_superuser, is_staff fields) `notebook` `notebook_revision` This is similar to what we did with treeherder way back when in bug 1279580. I think this is slightly lower priority than getting the production server fully up and running, but it would be nice to have this shortly after.