Commit 99f9d827 authored by Elliot Forbes's avatar Elliot Forbes 2️⃣ Committed by Amy Phillips
Browse files

Revamp the LabKit homepage to include a more succinct roadmap

parent 9b45c054
Loading
Loading
Loading
Loading
+28 −34
Original line number Diff line number Diff line
@@ -48,6 +48,34 @@ This section lays out a rough roadmap describing some of the sub-projects we are

If you have any questions or suggestions about projects you'd like to see in this list, please reach out to the [Development Tooling team](development-tooling/_index.md).

### Now

**Focus: Best-In-Class Logging For Internal Services** (FY27-Q1 to FY27-Q2)

- Ship production-ready logging packages for supported languages
- Drive adoption through [PREP](https://gitlab.com/gitlab-org/architecture/readiness/) and enforcement mechanisms
- Consolidate fragmented log schemas into consistent structure for cross-service debugging

### Next

**Focus: Metrics and Tracing** (FY27-Q2 to FY27-Q4)

- Extend observability foundations with standardized metrics and tracing packages
- Deliver composite abstractions that reduce boilerplate (e.g., auto-instrumented handlers)
- Enable correlation across logs, metrics, and traces by default

### Later

**Expanded Infrastructure Abstractions** (FY27-Q4+)

- Identify high-impact DevEx opportunities based on adoption feedback
- Candidate areas: HTTP/gRPC clients, queuing, caching, alert templates
- Prioritize based on pain points and time-to-production impact

## In-Flight Projects

This section encapsulates the current, in-flight projects that we're focused on delivering:

### Field Standardization

Status: **Under Development**
@@ -79,37 +107,3 @@ The goal is to standardise how logging is configured within our GitLab services.
- This will enable the Observability team to move faster in their efforts to adopt OTeL logging and again ties into **strengthening our monitoring and observability capabilities for managing GitLab** for both self-managed and SaaS.
- Initial investigations have also highlighted that we can improve the startup and runtime performance of our systems by migrating away from legacy logging libraries.
- This will also **accelerate customer value** as we’ll be leaning on modern industry standards for logging and subsequent feature development work should be faster.

### Metric Standardization

Status: **To Be Scheduled**

### Tracing Standardization

Status: **To Be Scheduled**

**Note:** this is pending the outcome of this open epic: [Select a distributed tracing solution for production use](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1517)

### Composite Metrics Functionality

Status: **To Be Scheuled**

### Snowplow Standardization

Status: **To Be Scheduled**

The goal of this work is to provide all developers with the ability to lean on our Snowplow setup in a standard, consistent way.

We currently have a few fragmented approaches to set up Snowplow for capturing events, GDK being one of them. The ideal outcome of this project is that
any internal team can lean on a generic setup should they need.

**Note:** Some work is [ongoing](https://gitlab.com/gitlab-org/labkit/-/merge_requests/259) to add an initial snowplow client to the LabKit Go repository, however, a wider effort will be needed to ensure that
we're catering for any and all internal use cases.

### Standardised health, liveliness and readines checks

Status: **To Be Scheduled**

### Standardised HTTP and gRPC Clients

Status **To Be Scheduled**