This is one of the few remaining MediaWiki key performance metrics still tied to Graphite.
Options to consider:
- Migrate to Prometheus as-is.
This means we keep the current stack of mw-navtiming.js -> dedicated analytics SaveTiming event schema -> EventLogging/EventGate -> navtiming.py, but adding -> Prometheus to the end of it.
- Migrate to statsv.
Frontend SaveTiming is a single number. If we migrate it to statsv it could prove a good candidate for T180105: Set up a statsv-like endpoint for Prometheus. This would make the stack much much simpler: mw-navtiming.js -> statsv -> Prometheus.
I'm tagging this with the MediaWiki Platform Team's Radar for visibility within my team as I'd likely assist in this as one of the first tasks to pair on with new owners of NavigationTiming and the navtiming.py service. We don't own this service.