-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doc needed: How to use this with apache daemon-mode processes? #77
Comments
Not sure if it's what you are asking but I made a PR about updating doc for multiprocess run: aeb891b It's for uwsgi but some of it can still be used for Apache. |
I completely missed that PR, sorry! I just merged it. |
@geobeau , Will everything simply work seamlessly on multi-process setups? i.e., if we have > 1 worker processes, will the counters returned by django-prometheus be aggregate across all workers? I found some documentation: https://github.com/korfuri/django-prometheus/blob/master/documentation/exports.md It's quite well documented for situations with multiple processes (that change a lot) under uWSGI, but not under Apache or Nginx. Is there any way we can add thos? |
Well I only used multiprocesses for uWSGI so I'm not sure about Apache/Nginx. If you set the env prometheus_multiproc_dir=/path/to/django_metrics in your django process it should work out of the box. So I would recommend that first you try just with that, then address the scalability issues if you have some. |
Hi,
I'm looking for documentation on how to use this with > 1 apache daemon mode processes.
Will all the metrics across all processes be aggregated by the main apache daemon and served at its port @ url /metrics?
Also, notes on the performance impact (roughly) per process.
The text was updated successfully, but these errors were encountered: