Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • runbooks runbooks
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Custom issue tracker
    • Custom issue tracker
  • Merge requests 101
    • Merge requests 101
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container 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.comGitLab.com
  • runbooksrunbooks
  • Repository
Switch branch/tag
  • runbooks
  • metrics-catalog
  • services
  • api.jsonnet
Find file BlameHistoryPermalink
  • Graeme Gillies's avatar
    Tweak metrics catalog so workhorse api metrics are correctly captured from Kubernetes · fcc3ab0b
    Graeme Gillies authored Mar 26, 2021
    Fixes https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/12946
    
    Part of gitlab-com/gl-infra/delivery#1464
    
    With the API service being migrated to Kubernetes, we need to expand the job selector
    we use to pickup workhorse metrics as the job name is different for API in Kubernetes
    fcc3ab0b