summaryrefslogtreecommitdiff
path: root/config.ru
Commit message (Collapse)AuthorAgeFilesLines
* set ENV['prometheus_multiproc_dir'] in config/boot.rb instead of config.ruPawel Chojnacki2017-06-151-3/+0
|
* Move Prometheus presentation logic to PrometheusTextPawel Chojnacki2017-06-021-1/+1
| | | | | | | | + Use NullMetrics to mock metrics when unused + Use method_missing in NullMetrics mocking + Update prometheus gem to version that correctly uses transitive dependencies + Ensure correct folders are used in Multiprocess prometheus client tests. + rename Sessions controller's metric
* Mark migration as requiring no downtimePawel Chojnacki2017-06-021-0/+1
| | | | | + Add spaces for four phases approach + fix InfluxDB rename
* Add Changelog fix textual description in config.ruPawel Chojnacki2017-06-021-1/+1
|
* Use only ENV for metrics folder locationPawel Chojnacki2017-06-021-3/+2
|
* Prometheus metrics first passPawel Chojnacki2017-06-021-5/+1
| | | | metrics wip
* Initial pass at prometheus monitoring.Kevin Lyda2017-06-021-0/+7
| | | | | | | | | | | | | | | | This is a step for #29118. Add a single metric to count successful logins. Summary types are not supported so remove Collector. Either we need to support the summary type or we need to create a multiprocess-friendly Collector. Add config to load prometheus and set up the Collector and the Exporter. Fix `Gemfile` as current prometheus-client gemspec is missing the `mmap2` dependency.
* Increase Unicorn memory limits to 300-350adjust-unicorn-memory-limitsYorick Peterse2016-01-201-2/+2
| | | | | | | Using this limit on GitLab.com it appears we're able to reduce response timings by about 620 milliseconds compared to the previous limit. See gitlab-org/gitlab-ce!2421 for more information.
* Use env variables for Unicorn memory limitsYorick Peterse2016-01-201-1/+4
| | | | | This makes it easier for users to use their own limits based on their server configuration.
* Disable Unicorn::WorkerKiller in non-production environmentsrs-no-killers-in-developmentRobert Speicher2015-05-271-4/+7
|
* Check specifically for Unicorn in rack config.ru fileДамјан Георгиевски2014-01-231-1/+1
| | | | | Don't assume that if the Rack server is not Passenger then it must be Unicorn. There are many other Rack servers in the world (uwsgi being one example that people use a lot). The reverse check is much more logical, i.e. check explicitly for Unicorn
* Fix 'uninitialized constant Unicorn' errordprolife2013-12-221-0/+1
|
* don't use unicorn worker killer if PhusionPassenger is definedJames Newton2013-12-201-4/+6
|
* Add unicorn-worker-killer with memory checkJacob Vosmaer2013-12-181-0/+6
| | | | | Conflicts: Gemfile.lock
* added RAILS_RELATIVE_URL_ROOT supportChris Frohoff2012-12-281-1/+4
|
* init commitgitlabhq2011-10-091-0/+4