Skip to content
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

Reports backend investigation #327

Open
kookster opened this issue Oct 2, 2018 · 0 comments
Open

Reports backend investigation #327

kookster opened this issue Oct 2, 2018 · 0 comments
Labels
Milestone

Comments

@kookster
Copy link
Member

kookster commented Oct 2, 2018

Have a look at how to actually generate reports into a downloadable form.
Here's a few techy questions to sort out off the top of my head, but the issue is for generally trying to figure out how to go about generating reports as a technical problem:

Will we use a new API method on castle to request a report, or is this a different endpoint, like a lambda?

Assuming this is an async process, for the API call, get back a callback url to check to see when it is done being created, or how do we let the user know in the metrics UI when this is ready?

Query the postgres db, or BQ directly?

Could be saved to a file on s3? or is it easier from the google cloud to use their storage?

This is also a user question, but could we make a google drive sheet for the final report instead of a csv file, or as an option?

@kookster kookster added the high label Oct 2, 2018
@kookster kookster added this to the Sprint Sandi milestone Oct 2, 2018
@kookster kookster modified the milestones: Sprint Sandi, Sprint Tamsin Oct 16, 2018
@svevang svevang removed this from the Sprint Ursula milestone Oct 30, 2018
@kookster kookster added this to the Sprint Xander milestone Dec 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants