Monitoring Team

Monitoring Team

On this page


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.

Team members

Person Role
Seth Engelhard Engineering Manager, Monitor
Ben Kochie Staff Backend Engineer, Monitor
Peter Leitzen Senior Backend Engineer, Monitor
Reuben Pereira Backend Engineer, Monitor
Logan King Backend Engineer, Monitor
Sarah Yasonik Backend Engineer, Monitor

Stable counterparts

Person Role
Clement Ho Frontend Engineering Manager, Monitor
Amelia Bauerly UX Designer, Monitor & Package
Sarah Voegeli Senior UX Designer, Monitor & Package
Ahmad Sherif Site Reliability Engineer, Monitor
Simon Knox Frontend Engineer, Monitor
Jose Ivan Vargas Frontend Engineer, Monitor
Adriel Santiago Senior Frontend Engineer, Monitor
Tristan Read Frontend Engineer, Monitor
Joshua Lambert Senior Product Manager, Monitor


The monitoring team is responsible for:

This team maps to Monitor.

How to work with Monitoring

Adding new metrics to GitLab

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, customer deployments, and whether any default alerting rules should be provided.

Recommended process for adding new metrics:

  1. Open an issue in the desired project outlining the new metrics desired
  2. Label with the ~Monitoring label, and ping @gl-monitoring for initial review
  3. During implementation consider:
  4. The Prometheus naming and instrumentation guidelines
  5. Impact on cardinality and performance of Prometheus
  6. Whether any alerts should be created
  7. Assign to an available Monitoring team reviewer

Repos we own or use

Async Daily Standups

The purpose of our async standups is to allow every team member to have insight into what everyone else is doing and whether anyone is blocked and could use help. This should not be an exhaustive list of all of your tasks for the day, but rather a summary of the major deliverable you are hoping to achieve. All question prompts are optional. We use the geekbot slack plugin to automate our async standup in the #g_monitor channel.

Team Calendar

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.