Menu

1 / 4

How I Fixed GitLab's Self-Hosted Observability Architecture and Earned Level 3 Contributor Status

DEV Community: ruby·Manish Kumar·1 day ago
#9oKHpdni
#devtoruby#devto#dev#js#gitlab
Reading 0:00
15s threshold

A deep dive into debugging SaaS-centric assumptions in enterprise codebases, improving self-hosted observability, navigating GitLab's CI pipelines, and contributing to one of the world's largest open-source Ruby on Rails applications.

Executive Summary

Repository: gitlab-org/gitlab

Work item: #638990 — Observability service name is derived incorrectly for self-hosted URLs

Merge request: !270580 — Derive O11y service name only for GitLab-hosted URLs

Status: Approved by staff engineers and technical writing reviewers; CI pipeline green

Reviewers: @jotolo_gl and @rsarangadharan

Community milestone: GitLab Level 3 Contributor

Reward: 150 GitLab reward credits

A small assumption in URL parsing can have consequences across an entire application. In this contribution, I fixed an observability configuration issue where self-hosted service URLs were incorrectly treated as GitLab SaaS tenant identifiers.

The work involved more than changing a Ruby method.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.