Using GitLab, you automatically get broad and deep insight into the health of your deployment.
We provide a robust monitoring solution to give GitLab users insight into the performance and availability of their deployments and alert them to problems as soon as they arise. We provide data that is easy to digest and to relate to other features in GitLab. With every piece of the devops lifecycle integrated into GitLab, we have a unique opportunity to closely tie our monitoring features to all of the other pieces of the devops flow.
We work collaboratively and transparently and we will contribute as much of our work as possible back to the open source community.
|Seth Engelhard||Engineering Manager, Monitor|
|Ben Kochie||Staff Developer, Monitor|
|Peter Leitzen||Senior Backend Developer, Monitor|
|R.P.||Backend Developer, Monitor|
|Clement Ho||Interim Frontend Engineering Manager, Distribution, Monitor & Packaging|
|Amelia Bauerly||UX Designer, Monitor|
|Jose Ivan Vargas||Frontend Engineer, Monitor|
|Adriel Santiago||Senior Frontend Engineer, Monitor|
|Joshua Lambert||Senior Product Manager, Monitor|
The monitoring team is responsible for:
This team maps to Monitor.
The Monitoring team is responsible for providing the underlying libraries and tools to enable GitLab team members to instrument their code. When adding new metrics, we need to consider a few facets: the impact on GitLab.com, customer deployments, and whether any default alerting rules should be provided.
Recommended process for adding new metrics:
We use the Monitoring Team calendar to communicate when team members are traveling, attending conferences, and taking time off. If you do not have the appropriate access to the Monitoring Team calendar, please raise it in the
#g_monitor channel on Slack and someone will share it with you.