Skip to content

Use multiprocess_mode max for migrations Gauges#499

Open
olzhasar-reef wants to merge 1 commit into
django-commons:masterfrom
olzhasar-reef:gauges-multiprocess
Open

Use multiprocess_mode max for migrations Gauges#499
olzhasar-reef wants to merge 1 commit into
django-commons:masterfrom
olzhasar-reef:gauges-multiprocess

Conversation

@olzhasar-reef

@olzhasar-reef olzhasar-reef commented Feb 13, 2026

Copy link
Copy Markdown

By default, when using prometheus client in a multiprocess mode, Gauges
export a separate time series per pid. For migrations gauges, it makes
more sense to have a single timeseries for all processes, calculated by
taking a maximum of all values.

Closes #498

By default, when using prometheus client in a multiprocess mode, Gauges
export a separate time series per pid. For migrations gauges, it makes
more sense to have a single timeseries for all processes, calculated by
taking a maximum of all values.
olzhasar-reef added a commit to reef-technologies/cookiecutter-rt-django that referenced this pull request May 15, 2026
Migration exports lead to infinitely growing cardinality metrics when
using prometheus in the multiprocess mode. Disabling until the issue is
addressed in the library code

See:
django-commons/django-prometheus#498

and:
django-commons/django-prometheus#499
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Multiprocess mode for migration gauges

1 participant