Skip to content

GitLab Next

    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 is launching on May 22! This version brings many exciting improvements, but also removes deprecated features and introduces breaking changes that may impact your workflow. To see what is being deprecated and removed, please visit Breaking changes in 15.0 and Deprecations.

  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #29118
Project 'gitlab-org/gitlab-ce' was moved to 'gitlab-org/gitlab-foss'. Please update any links and bookmarks that may still have the old path.
Closed
Open
Created Mar 07, 2017 by Kevin Lyda@lydaContributor4 of 8 tasks completed4/8 tasks

Adding prometheus instrumenting to gitlab webapp

Description

Instrument Gitlab using the prometheus API to make it easier to track, detect and manage issues with Gitlab.

Once instrumenting is added it becomes possible to scrape Gitlab in order to detect performance issues, changes in performance, reliability issues, debug problems, spot performance trends across versions or over uptime.

Proposal

Steps to integrating this:

  • Create a multi-proccess mode for the existing ruby prometheus library.
  • Update the existing ruby prometheus library to current standards. Being tracked in: client_ruby issue 9.
  • Have a way to set the prometheus_multiproc_dir environment variable within unicorn.
  • Document 'prometheus_multiproc_dir' usage
  • Link 'prometheus_multiproc_dir' in config.ru and Application Settings in Rails app
  • Metrics endpoint name.
  • There's some existing influx instrumentation - make use of that.
  • Work with gitlab.com production engineering to find important metrics that are required.

Links / references

Edited Jul 25, 2017 by Paweł Chojnacki
Assignee
Assign to
Time tracking