Monitor Stage

The Analytics Instrumentation group work on feature enhancements and implementing privacy focused product analytics across GitLab projects

Who we are?

The Platform Insights group is part of the GitLab Monitor stage and builds GitLab Observability and Product Analytics products.

Team members

Name	Role
Nicholas Klick	Engineering Manager, Monitor:Platform Insights
Ankit Bhatnagar	Staff Backend Engineer, Monitor:Platform Insights
Arun Sori	Senior Backend Engineer, Monitor:Platform Insights
Daniele Rossetti	Senior Frontend Engineer, Monitor:Platform Insights
Jiaan Louw	Senior Frontend Engineer, Monitor:Platform Insights
Mat Appelman	Principal Engineer, Monitor
Max Woolf	Staff Backend Engineer, Monitor:Platform Insights
Robert Hunt	Staff Frontend Engineer, Monitor:Platform Insights

Stable counterparts

Name	Role
Principal Engineer	Principal Engineer, Monitor
Lindsy Farina	Senior Product Manager, Monitor:Platform Insights
Ottilia Westerlund	Security Engineer, Fulfillment (Fulfillment Platform, Subscription Management), Security Risk Management (Security Policies, Threat Insights), Monitor (Observability), Plan (Product Planning), AI-powered (Duo Chat, Duo Workflow, AI Framework, AI model validation, Custom models)

Technical Architecture

Architecture Blueprints

• Error Tracking
• Tracing
• Metrics
• Logs

Architecture Documentation

• See this page

Project Links

• Top-level Epic
• Source Code Repository

ClickHouse Datastore

Observability and analytics features have big data and insert heavy requirements which are not a good fit for Postgres or Redis. ClickHouse was selected as a good fit to meet these features requirements. ClickHouse is an open-source column-oriented database management system. It is attractive for these use cases because it can efficiently filter, aggregate, and sum across large numbers of rows. ClickHouse is not intended to replace Postgres or Redis in GitLab’s stack.

Plan:Optimize

Optimize FY25 direction and goals

How we work

• In accordance with our GitLab values.
• Transparently: nearly everything is public, we record/livestream meetings whenever possible.
• We get a chance to work on the things we want to work on.
• Everyone can contribute; no silos.
  • The goal is to have product give engineering and design the opportunity to be involved with direction and issue definition from the very beginning.
• We do an asynchronous daily stand-up in our group stand-up channel:
  • #g-optimize-engineers-standup
• You can reach out to the team on slack at: #g_plan_optimize

Prioritization

Our priorities should follow overall guidance for Product. This should be reflected in the priority label for scheduled issues: