Unified Engineering Dashboard - Cross-Organizational Metrics

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Overview

Collaborate on creating a unified cross-organizational Engineering Dashboard that combines multiple existing dashboards and engineering metrics into a single platform for engineering leadership visibility across GitLab.

Goal

Create a consolidated engineering dashboard that brings together metrics and dashboards from across the organization:

  1. Quality Metrics - SLO compliance, S1/S2 bug tracking, flaky tests, milestone commitments
  2. Support Load Reduction - Escalation tracking, support ticket trends
  3. Engineering Metrics - Kanban flow, cycle time, throughput
  4. Observability - Existing GitLab observability dashboard integration

The aim is to provide a single pane of glass that any section or team can plug into, not limited to a single section.

Existing Dashboards to Consolidate

Dashboard Owner URL
Quality Dashboard @alan / @mmishaev https://sec-escalation-reduction-b7f176.gitlab.io/quality/
Kanban Dashboard @ghosh-abhinaba https://gitlab-snap-338f89.gitlab.io/
Kanban Dashboard Source @ghosh-abhinaba https://gitlab.com/gitlab-org/growth/growth-playground/gitlab-snap
GitLab Observability Dashboard - https://gitlab.com/groups/gitlab-org/-/observability/dashboard
SaaS Health Metrics @rnienaber https://saas-health-83948d.gitlab.io/
DX Insights Dashboard @pjphillips DX Insights dashboard (gitlab-org/quality#347)

Data Sources

  • Quality data: Generated weekly via automated scripts (quality repo) - JSON format available at quality_data.json
  • Support metrics: Tracked in the sec-escalation-reduction project
  • Engineering metrics: Kanban board data from growth-playground
  • GitLab API: Direct integration for real-time data
  • Incident Information: Incident.io

Proposed Approach

  1. Phase 1: Define unified data schema that is extensible across sections/teams
  2. Phase 2: Build combined frontend consuming all data sources with pluggable modules
  3. Phase 3: Automate data refresh and deploy via GitLab Pages
  4. Phase 4: Onboard additional sections and teams

Success Criteria

  • Single dashboard URL for cross-organizational engineering health
  • Modular design - any section/team can plug in their metrics
  • Auto-refreshed data (daily or weekly)
  • Covers quality, support, and engineering velocity metrics
  • Accessible to all engineering leadership

/cc @ghosh-abhinaba @nitinsinghal74 @maw

Edited by Paul Phillips