To ensure we don't let our editors wait too long while opening a CommunityConfiguration edit form, we should track the time until that is available.
Acceptance criteria:
- the time until the form is ready is tracked per provider
- there exists a panel on Grafana showing percentiles
Open questions:
- what should be our start time? I think the mwStartup performanceMark makes sense and removes some of the things that are not under our control anyway
- which percentiles do we want to show on Grafana? 50%, 95%, 99.5%?
- what exactly should the metric name be?
- probably the Grafana board should a variable for the provider?
- do we want to split by wiki?
Notes:
- One other candidate for a metric to track in practice, Largest Contentful Paint (LCP), turns out to not be a great choice, because it does not seem to actually identify the form as the "largest image or text block" and instead only measures the time for the server-rendered description (<p>-element) that sits above the form.
- "the form is ready" would probably be the end of the IIFE in init.js, after the createApp method returned
- using mw.track.timing to record this
- if we use the mwStartup mark, then performance.measure('CommunityConfigurationEditFormLoaded', 'mwStartup').duration should give us time we want to track