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

docs: lighthouse as a service #6008

Merged
merged 2 commits into from
Sep 18, 2018
Merged

Conversation

asilvas
Copy link
Contributor

@asilvas asilvas commented Sep 12, 2018

Sponsored by GoDaddy. We use this service to monitor thousands of new or modified websites every day.

https://github.com/godaddy/lighthouse4u

Sponsored by GoDaddy. We use this service to monitor thousands of new or modified websites every day.
@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

@asilvas
Copy link
Contributor Author

asilvas commented Sep 12, 2018

I signed it!

@googlebot
Copy link

CLAs look good, thanks!

@asilvas asilvas changed the title LH4U: Lighthouse as a service lighthouse as a service Sep 12, 2018
@asilvas asilvas changed the title lighthouse as a service docs: lighthouse as a service Sep 12, 2018
@paulirish
Copy link
Member

this is very cool! nice work!

I'm curious about the visualization side. Do you have anything currently setup with kibana? What else are you thinking about?

@asilvas
Copy link
Contributor Author

asilvas commented Sep 12, 2018

Yes we do have generic visualizations broken out by groups/categories.

image

The dashboard is nothing special, but could potentially provide to help save some time.

LH4U provides test isolation (versus in cicd pipelines where slaves are often competing for resources), provides us pre-RUM synthetics enabling us to hook into our PR pipelines and block merges, and supports secured apps (basic auth, JWT, etc).

Copy link
Member

@paulirish paulirish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

btw is that plot something that comes for free with l4u, or did you configure it against the ES data?

readme.md Outdated
@@ -287,6 +287,7 @@ Other awesome open source projects that use Lighthouse.
* **[lighthouse-security](https://github.com/voorhoede/lighthouse-security#readme)** - Run a set of security audits along with Lighthouse.
* **[Garie](https://github.com/boyney123/garie)** — An open source tool for monitoring performance using Lighthouse, PageSpeed Insights, [Prometheus](https://prometheus.io/), [Grafana](https://grafana.com/) and [Docker](https://www.docker.com/).
* **[lighthouse-ci](https://github.com/andreasonny83/lighthouse-ci)** - Run Lighthouse and assert scores satisfy your custom thresholds.
* **[lighthouse4u](https://github.com/godaddy/lighthouse4u)** - LH4U provides Google Lighthouse as a service, surfaced by both a friendly UI+API, and backed by Elastic Search for all your query and visualization needs.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"for all your query and visualization needs"
⬇️
"for easy querying and visualization"

@asilvas
Copy link
Contributor Author

asilvas commented Sep 18, 2018

@paulirish It's just a basic view I setup in Kibana (trivial task), which is not currently included in LH4U. Once we have a better idea of how folks want to visualize this data we can create a Kibana dashboard for importing. Out of the box we only save to Elasticsearch; how that data is consumed/visualized is up to you.

@paulirish
Copy link
Member

@asilvas roger that. just checking. :) thanks

@paulirish paulirish merged commit a0c8e3e into GoogleChrome:master Sep 18, 2018
@asilvas asilvas deleted the patch-1 branch September 18, 2018 21:45
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

Successfully merging this pull request may close these issues.

None yet

3 participants