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

Use Lighthouse tables from BQ #3

Open
ebidel opened this issue Jun 30, 2017 · 4 comments
Open

Use Lighthouse tables from BQ #3

ebidel opened this issue Jun 30, 2017 · 4 comments

Comments

@ebidel
Copy link
Owner

ebidel commented Jun 30, 2017

LH specific tables now:
https://bigquery.cloud.google.com/table/httparchive:har.2017_06_20_android_lighthouse?pli=1&tab=preview

ebidel added a commit that referenced this issue Jun 30, 2017
@ebidel
Copy link
Owner Author

ebidel commented Jun 30, 2017

Keeping this open b/c it isn't pushed yet. The 6/20 table only has 18 lh report, which is not enough to show meaningful data.

@rviscomi
Copy link

rviscomi commented Sep 5, 2017

LH data in HTTP Archive has been collected regularly since 6/1 under the _android_lighthouse suffix. There's also a convenience table latest_lighthouse_mobile which aliases the most recent results.

I've also generated a one-off table with a more LH specific schema, so you could query by category, audit, and score: scratchspace.2017_06_15_lighthouse_audits. If this kind of table would be useful, let's chat about a schema that works best for you and I can help get the table generated regularly. Then on this end, we'd just need to modify the query to pull from the new tables.

@ebidel
Copy link
Owner Author

ebidel commented Sep 5, 2017

@brendankenny has been generating LH-specific tables too. Do you think we should has @rviscomi take that over for us?

@brendankenny
Copy link

yeah, I can share the query I use (it's big) if we want a more official table with a LH-specific schema, though I'll likely keep generating my side tables since we keep adding checks for things of LH-development interest (e.g. rates of specific error types) that change every time we release a new version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants