As a follow up to T290019 lets create a new schema for Navigation Timing data and keep navigation timing and other performance related metrics in that schema.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T319329 Expand navigation timing metrics to include user experience metrics and modernise navigation timing | |||
| Resolved | Peter | T295684 Create new schema for Navigation Timing (+more) data |
Event Timeline
Comment Actions
Reading https://calendar.perfplanet.com/2021/using-diagnostic-metrics/ we should keep a way to bucket LCP/CLS values depending on which element that is involved. I was thinking that we should just skip that but as Annie says it should be handy.
Comment Actions
Also adding https://web.dev/debug-web-vitals-in-the-field/ since there are some interesting things in there.
Comment Actions
This might be a good one to do in combination with T175087: Create a navtiming processor for Prometheus, e.g decide how we want to structure it in Prometheus, and work our way backwards to a simple and minimal ingestion pipeline from there.
Comment Actions
We think we can consider this done as a part of the work we did with Prometheus. We updated the current schema to include all the new metrics.