As discussed earlier this week, we plan to use a SWAT deploy on Monday the 18th to stop this test for now, now that the planned two weeks are complete.
@Tbayer, @phuedx - are we sure we're ready for this given what we've seen in T175918: EventLogging subscriber module in ready state but not sending tracked events - or is Firefox safe from that bug? (in which case, let's go ahead as planned)
Given the additional strain that we've put on the EventLogging pipeline during the last two weeks (a peak rate of 19.32K events/min!!1), I felt that we stop logging events at the pre-agreed time. If we conclude that T175918: EventLogging subscriber module in ready state but not sending tracked events has impacted the data that we've collected, then we should re-run the A/B test with a fix in place.