This will likely require merging the ServerTiming EventLogging schema into the https://meta.wikimedia.org/wiki/Schema:NavigationTiming one, so that the navtiming daemon can get this data in the same record it currently collects the responseStart metric from.
|Resolved||ema||T264398 8-10% response start regression (Varnish 5.1.3-1wm15 -> 6.0.6-1wm1)|
|Resolved||• Gilles||T264987 Add cache response type and response size as new dimensions to navtiming_responsestart_by_host_seconds prometheus metric|
The new cacheReponseType field is being collected correctly in Hive:
SELECT COUNT(*), event.cacheResponseType FROM event.navigationtiming WHERE year = 2020 AND month = 11 AND day = 30 GROUP BY event.cacheResponseType; _c0 cacheresponsetype 104711 NULL 158735 hit-front 3508 hit-local 78574 miss 20267 pass
NULL responses are from browsers that don't support Server Timing.
And as expected the ServerTiming schema no longer collects data:
SELECT COUNT(*) FROM event.servertiming WHERE year = 2020 AND month = 11 AND day = 30; _c0 10
Those 10 hits are probably stragglers from people with old JS cached (eg. frozen browser tab reawakened).