This umbrella task will be used to track production launch of "client side error logging" project.
Paraphrasing from https://etherpad.wikimedia.org/p/clients-error-logging, we'll be lining up as many ducks as we can in Q1, with launch in Q2 to many/most wikis. End of Q2 is naturally risking for high traffic wikis because of donation campaigns, we'll have to weight benefit/risks of launching to big wikis too.
- Schema validation for eventgate events
- kubernetes setup for eventgate deployment (i.e. backend component) initially set to receive errors from low traffic wikis - @Ottomata
- Write minimal client to send errors without attempting normalization for MVP
- Security review of the js client we'll be using, preliminary task at T232820
- Performance review of the js client we'll be using (Timo reviewed code)
- Verify we have enough ingestion capacity on the Logstash side @fgiunchedi
- Deploy and enable on one low traffic wiki - T246030
- Related to the above, make sure deduplication/rate limiting in depth (i.e. both on the client side, and on the backend side) is in place before high traffic wikis launch.
- Verify events show up in logstash and we have a Kibana dashboard available @fgiunchedi
@dr0ptp4kt @phuedx @Ottomata @Milimetric @CDanis @colewhite @Tgr @Krinkle please check and adjust the above plan as needed! What do you think?