Frontend Observability Working Group
|Date Created||2021-07-14 (Paused from 2022-06-01 to 2023-02-24)|
|Slack||#wg_frontend-observability (only accessible from within the company)|
|Google Doc||Working Group Agenda (only accessible from within the company)|
|Overview & Status||Epic|
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.
Scope and Definitions
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 automatically via renovate Link
- Sentry is configured to track and report frontend errors reliably Link
- Sentry is configured to monitor our performance with performance tracing Link
- A triaging / diagnosing process is created for sentry errors Link
- Documentation is written that allows other frontend engineers to contribute Link
- The old sentry settings are deprecated and removed Link
Roles and Responsibilities
The functional leads will be responsible for:
- Representing the needs of individual stakeholders in their department/sub-dept
- Gathering and consolidating feedback on specific proposals from their department/sub-dept
- Communicating the output from the working group (if any) and answering questions from their dept/sub-dept
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||Development||Senior Director|
|Facilitator||Sam Beckham||Manage:Foundations||Engineering Manager|
|Functional Lead||Miguel Rincon||Verify::Runner||Senior Frontend Engineer|
|Functional Lead||Drew Stachon||Verify::Pipeline Execution||Backend Engineer|
|Functional Lead||Andrew Newdigate||Infrastructure||Distinguished Engineer|
|Member||José Vargas López||Verify::Pipeline Execution||Senior Frontend Engineer|
|Member||Marius Bobin||Verify::Pipeline Execution||Backend Engineer|
|Member||Daniele Rossetti||Monitor::Visualization||Senior Frontend Engineer|
|Member||Sheldon Led||Fulfillment||Senior Frontend Engineer|
|Member||Adeline Yeung||Infrastructure||Site Reliability Engineer|
|Member||Rahul Chanila||Package||Senior Frontend Engineer|
|Member||Savas Vedova||Govern||Senior Frontend Engineer|