summaryrefslogtreecommitdiff
path: root/config/initializers/7_prometheus_metrics.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-07-221-0/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-05-281-4/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-05-221-4/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-05-201-0/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-05-151-0/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-04-211-0/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-091-0/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-221-6/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-171-6/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-161-9/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-111-6/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-071-0/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-301-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-161-1/+9
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-161-0/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-041-1/+22
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-021-0/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-171-2/+4
|
* Clean Sidekiq metrics from multiproc dir on startAleksei Lipniagov2019-08-191-0/+3
| | | | | | | After moving the multiproc dir cleanup into `config.ru`:`warmup`, we stopped cleaning Sidekiq metrics dir which is not correct. This MR intended to fix that. More details: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31668
* Fix metric files being wiped after the app startsAleksei Lipniagov2019-08-121-19/+0
| | | | | | | | | When we hit our app with the initial request, in `warmup`, some metrics already being created as well as corresponding files. If we do `multiproc_file_dir` cleanup after that, we delete the files from the dir while keeping them in memory which leads to the incorrect behavior: the metric is being updated in in-memory, while is not present in the db, not sent to Prometheus as the result.
* Fix pid providing for PrometheusAleksei Lipniagov2019-07-181-2/+1
| | | | | | | Use relative worker identifier for metrics (instead of Process.pid) and identify when Unicorn/Puma/Sidekiq is used. Previously, it was assumed that all metrics are gathered from Unicorn due to hardcoded implementation which was incorrect.
* Add a rubocop for Rails.loggerMayra Cabrera2019-07-101-1/+1
| | | | | | Suggests to use a JSON structured log instead Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
* Merge branch ↵Kamil Trzciński2019-07-021-4/+16
|\ | | | | | | | | | | | | | | | | '63869-store-prometheus-metrics-in-separate-dirs-in-test-and-prod' into 'master' Use separate Prometheus metrics dirs in dev/test Closes #63869 See merge request gitlab-org/gitlab-ce!30253
| * Use separate Prometheus metrics dirs in dev/test63869-store-prometheus-metrics-in-separate-dirs-in-test-and-prodAleksei Lipniagov2019-07-021-4/+16
| | | | | | | | | | Store Sidekiq and Web server metrics from Prometheus in separate directories in `development` and `test` environments.
* | Start UnicornSampler in master processJan Provaznik2019-07-021-6/+4
|/ | | | | Using `on_master_start` assures that the sampler is started in master process and not in worker processes.
* Run do_master_restart callback on server startJan Provaznik2019-07-011-4/+11
| | | | | | | | | | We want to call master_restart callback on start too - this callback is used for cleaning up prometheus files. It has been added to Omnibus already: https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3350 So make sure that Unicorn example configs are up-to-date and that the same callback is called for Puma too.
* Add back sidekiq metrics exporterrc/add_back_sidekiq_exporterRyan Cobb2019-06-131-0/+6
|
* Adds sidekiq worker label for ruby metricsRyan Cobb2019-06-061-6/+0
|
* Add Puma samplerJan Provaznik2019-05-291-1/+7
| | | | | This sampler gathers Puma-specific metrics which can be used by Prometheus then.
* Add experimental support for Pumaan-multithreadingAndrew Newdigate2018-10-251-3/+19
| | | | | | This allows us (and others) to test drive Puma without it affecting all users. Puma can be enabled by setting the environment variable "EXPERIMENTAL_PUMA" to a non empty value.
* Disable the background Prometheus sampler in testssh-disable-background-metrics-in-testsStan Hu2018-05-241-1/+1
| | | | | This sampler can interfere with tests and cause transient build failures, such as https://gitlab.com/gitlab-org/gitlab-ce/-/jobs/70241683.
* Update prometheus-client-mmap gem to highly optimized versionPawel Chojnacki2017-12-071-8/+1
| | | | | + change string concatenation to help with GC pressure. + fix metric producing incompatible label sets
* Rename wip to worker_idPawel Chojnacki2017-11-231-3/+3
|
* Move prometheus middle ware to prometheus initialized.Pawel Chojnacki2017-11-231-1/+5
|
* Only enable unicorn metrics when not in sidekiq mode.Pawel Chojnacki2017-11-021-1/+4
| | | | + remove rebased test case
* Cleanup transaction metricsPawel Chojnacki2017-11-021-4/+13
|
* Finished Ruby SamplerPawel Chojnacki2017-11-021-1/+1
| | | | + Cleanup sampler, use latest Prometheus gem
* Add GC sampler and small refactor of samplersPawel Chojnacki2017-11-021-0/+4
|
* Update Prometheus Client MMAP gem to version that fixes performance ↵pawel/bump_prometheus_client_mmap_version_to_fix_performance_degradationPawel Chojnacki2017-08-291-0/+3
| | | | degradation caused by workers churn
* Add sidekiq metrics endpoint and add http server to sidekiqPaweł Chojnacki2017-08-071-0/+6
|
* Ensure test files are deleted after testsPawel Chojnacki2017-07-251-1/+1
|
* Update Prometheus gem to version that explicitly calls `munmap`Paweł Chojnacki2017-07-191-0/+12