Change Details

As a product owner, I want to avoid logging events at a high sampling threshold for a long period, so that my queries run faster and we use less disk space. As per T123980#2035526, this is a task to return the language switcher instrumentation back down to 1/10,000 sample-in on the stable channel after several days (two full weekend days and one full weekday, minimally) of data have been captured at a higher 1/1,000 sample-in rate for the A/B test of the structured modal.

As a product owner, I want to avoid logging events at a high sampling threshold for a long period, so that my queries run faster and we use less disk space. This should be deployed once //both// the new language switcher button affordance and language switcher overlay have been in production for a couple weeks.

As a product owner, I want to avoid logging events at a high sampling threshold for a long period, so that my queries run faster and we use less disk space. As per T123980#2035526, this is a task to return the language switcher instrumentation back down to 1/10,000 sample-in on the stable channel after several days (two full weekend days and one full weekday, minimally) of data have been captured at a higher 1/1,000 sample-in rate for the A/B test of the structured modalThis should be deployed once //both// the new language switcher button affordance and language switcher overlay have been in production for a couple weeks.