|Matt Nohr||Engineering Manager, Monitor APM|
|Reuben Pereira||Backend Engineer, Monitor|
|Ryan Cobb||Backend Engineer, Monitor|
|Adrien Kohlbecker||Senior Backend Engineer, Monitor APM|
|David Wilkins||Backend Engineer, Monitor|
|Adriel Santiago||Interim Frontend Engineering Manager, Monitor APM|
|Jose Ivan Vargas||Frontend Engineer, Monitor APM|
|Dhiraj Bodicherla||Senior Frontend Engineer, Monitor APM|
|Miguel B.||Senior Frontend Engineer, Monitor APM|
|Achilleas Pipinellis||Technical Writer, Create, Package, Monitor, Secure, Defend|
|Amelia Bauerly||Product Designer, Monitor & Package|
|Sarah Voegeli||Senior Product Designer, Monitor & Package|
|Ahmad Sherif||Site Reliability Engineer, Manage, Monitor & Configure|
|Amarbayar Amarsanaa||Senior Site Reliability Engineer, Create, Plan, Monitor|
|D.H.||Senior Product Manager, Monitor:APM|
|Sarah Waldner||Product Manager, Monitor:Health|
|bg||Product Marketing Manager, Monitoring, Create|
The APM group is responsible for:
This team maps to the APM Group category and focuses on:
The Monitor Group 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:
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_standup channel.
While we try to keep our process pretty light on meetings, we do have a few recurring meetings to keep in sync and to keep our backlog in good shape. We hold the Monitor Group Weekly Meeting to discuss agenda items that have been added over the course of the week and to walk through our current issue board together.
There is also an optional Monitor Social Hour meeting every week. This call has no agenda and alternates times every other week to be more inclusive of team members in different time zones.
Just like the rest of the company, we use PTO Ninja to track when team members are traveling, attending conferences, and taking time off. The easiest way to see who has upcoming PTO is to run the
/ninja whosout command in the
#g_monitor_standup slack channel. This will show you the upcoming PTO for everyone in that channel.