Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gitlab-workhorse gitlab-workhorse
  • 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
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitlab-workhorsegitlab-workhorse
  • Issues
  • #61
Closed
Open
Created Sep 16, 2016 by Jacob Vosmaer@jacobvosmaer-gitlabMaintainer

Expose service metrics via Prometheus

Using https://github.com/prometheus/client_golang we can add an HTTP listener to gitlab-workhorse and expose counters etc. to be scraped by Prometheus. For instance, the number of requests served broken down by HTTP method.

Before I spend more time on this I would like to know who/what should have access to this HTTP endpoint. Not the whole world.

I think securing / configuring access to the new HTTP end point is the 'hard part' of adding Prometheus support to gitlab-workhorse.

@pcarranza do we already have something in place that scrapes Prometheus endpoints behind the firewall on gitlab.com boxes? If not what would this look like?

I don't think it makes sense to add the workhorse support for this until we understand what we need on gitlab.com.

Assignee
Assign to
Time tracking