James C Scott III

Results came in the following day

@foolip thanks so much for these steps. I can take a look into the processor's logs in GCP.

Some raw notes from the investigation: ```js { insertId: "14iltpfgnk6as" logName: "projects/wptdashboard/logs/request_log_entries" receiveTimestamp: "2022-07-26T05:05:49.245405560Z" resource: {2} severity: "ERROR" textPayload: "Failed to fetch check runs for suite 7515393036: GET https://api.github.com/repos/web-platform-tests/wpt/check-suites/7515393036/check-runs?page=7&per_page=25: 502...

After #2927 happened. It was confirmed that the Google Aanlytics 4 wptdashboard is now populating.

For the universal analytics, by default it includes all traffic to any deployment of wpt.fyi (localhost, staging, prod, any custom deployments) I created a custom segment to filter only on...

Here's the segment: https://analytics.google.com/analytics/web/template?uid=TRn3Ezh2Sj6phuBlI2DlQw (Can only share by link or put it publicly in the Solutions Gallery for all Google Analytics users to import)  I like your comment about...

Did some initial investigation. Seems like Google Analytics 4 right now is counting redirects as page views. This can lead to two views for a particular page (e.g Scenario 1)....

I did some more analysis into the scenarios where it counts as two events. (1 redirect and 1 actual destination with the added query parameters) Google Analytics 4 is acting...

Reason why the deploy still fails upon retriggering: https://github.com/web-platform-tests/wpt.fyi/issues/2928

Reason why the deploy still fails upon retriggering: https://github.com/web-platform-tests/wpt.fyi/issues/2928