You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 25, 2023. It is now read-only.
On the old demo dashboard, we had a nice graph showing the slowest assets, over time.
It was nice because it could be used to look at the availability and performance of the 3rd party (and some slow 1st party resource).
We could produce at least for the public demo a graph showing the response time per domain (it will probably store less data). It wont tell much about 1st party resources having troubles, but in my case it will be enough to monitor how 3rd parties scripts are performing.
The text was updated successfully, but these errors were encountered:
Yes I see your point @jpvincent . One of the main issues with 4.0 was that it generated too much data by default into Graphite. Let us update the documentation to how to send the metrics as first step and then maybe setup one more dashboard (or include in the current 3rd party dashboard).
hi @gajus
I ended up implementing it by creating a dashboard and enabling more metrics to be sent to graphite, I added a code example here : sitespeedio/sitespeed.io#1277
I can confirm it does take a lot of storage space though, be careful
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On the old demo dashboard, we had a nice graph showing the slowest assets, over time.
It was nice because it could be used to look at the availability and performance of the 3rd party (and some slow 1st party resource).
We could produce at least for the public demo a graph showing the response time per domain (it will probably store less data). It wont tell much about 1st party resources having troubles, but in my case it will be enough to monitor how 3rd parties scripts are performing.
The text was updated successfully, but these errors were encountered: