|Slack||#wg_frontend-observability (only accessible from within the company)|
|Google Doc||Working Group Agenda (only accessible from within the company)|
This working group will co-ordinate the organization of the effort to develop a frontend observability framework for Gitlab and establish guidelines for its usage. There is currently no method to instrument the frontend for the purposes of monitoring performance, especially across a range of devices and content. Error monitoring is possible but is mostly unused. This group will explore, define, and coordinate the development of system to make this instrumentation possible and document recommendations for use.
This group will focus on creating a method for sending browser performance data to a frontend stats gateway that will allow the metrics to be accessed via our system, like the current backend metrics. Determining the details of this is part of the remit. Once this exists, the group will be responsible for documenting its use, as well as usage recommendations for error monitoring. This will allow frontend engineers to understand the performance of their code in various contexts and add another source of data to help find issues when new features are rolled out.
Stakeholders for this project include frontend engineers and SREs.
This group will not focus on instrumentation around user actions for product reasons; this is covered by Snowplow and has a different use case.
This working group will have fulfilled its purpose when:
@sentry/browserpackage is upgraded to version
The functional leads will be responsible for:
Ideally the functional lead is someone who is an IC that might be affected by the policy put in place. but anyone capable of representing a department or sub-department in the fashion mentioned above is welcome.
|Working Group Role||Person||Stakeholder Department||Title|
|Executive Sponsor||Tim Zallmann||Senior Director|
|Facilitator||Sam Beckham||Frontend:Verify||Frontend Engineering Manager|
|Functional Lead||Sarah Groff Hennigh-Palermo||Frontend:Verify::Pipeline Authoring||Senior FE Engineer|
|Functional Lead||Drew Cimino||Backend:Verify::Pipeline Execution||Backend Engineer|
|Functional Lead||Andrew Newdigate||Infrastructure||Distinguished Engineer|
|Member||José Vargas López||Frontend:Verify::Pipeline Execution||Senior FE Engineer|
|Member||Thomas Randolph||Frontend:Create::Code Review||Senior FE Engineer|
|Member||Daniel Fosco||Design:Release::Release||Senior Product Designer|
|Member||Marius Bobin||Backend:Verify::Pipeline Execution||Backend Engineer|
|Member||Miguel Rincon||Frontend:Verify::Runner||Senior FE Engineer|
|Member||Dov Herskhovitch||Product Manager:Verify::Pipeline Authoring||Senior Product Manager|