Skip to content

Enable external Puma metrics server everywhere

Matthias Käppler requested to merge mk-puma-external-metrics-server into master

What does this MR do?

We are externalizing the Prometheus metrics server for Puma to run in a separate process, as we did with Sidekiq already.

The change is behind an env var, PUMA_EXTERNAL_METRICS_SERVER.

This MR enables this env var everywhere.

I have provided a short rollout plan here: gitlab-org/gitlab#350548 (closed)

Change mgmt issue: gitlab-com/gl-infra/production#6658 (closed)

Related MRs:

Author Check-list

Please read the Contributing document and once you do, complete the following:

  • Assign to the correct reviewer per the contributing document
  • Apply the correct metadata per the contributing document
  • Link to related MRs for applying the changes on other environments
  • Link to related Chef changes
  • If necessary link to a Criticality 4 Change Request issue

Reviewer Check-list

  • Reviewed the diff jobs to confirm changes are as expected
  • No changes shown in the diffs not associated with this MR - This may require a rebase or further investigation

Applier Check-list

  • Make sure there is no ongoing deployment for the affected envs before merging (see #announcements slack channel)
Edited by Henri Philipps

Merge request reports