We collect the effectiveConnectionType from user's browsers (when available), but we don't actually use that as a dimension when we create metrics in graphite. We should start to do so.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T343020 Converting MediaWiki Metrics to StatsLib | |||
| Open | None | T355837 Add Prometheus support to statsd.js via mw.track() | |||
| Open | None | T180105 Set up a statsv-like endpoint for Prometheus | |||
| Open | None | T228380 Tech debt: sunsetting of Graphite | |||
| Open | colewhite | T205870 Fully migrate producers off statsd | |||
| Open | None | T319329 Expand navigation timing metrics to include user experience metrics and modernise navigation timing | |||
| Open | None | T175087 Create a navtiming processor for Prometheus | |||
| Declined | None | T190936 navtiming.py: When processing metrics, include effectiveConnectionType as a factor |
Event Timeline
Comment Actions
This is about creating a new breakdown by connection type, like we have for whitelisted countries, right?
Comment Actions
This can be done in the Prometheus migration, but it is already available in Hive and turnilo.