Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2022-08-18 | 1 | -0/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2022-03-25 | 1 | -19/+9 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-05-26 | 1 | -60/+0 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-06-24 | 2 | -2/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-22 | 1 | -14/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-17 | 1 | -4/+14 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-11 | 1 | -14/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-22 | 1 | -1/+11 |
| | |||||
* | Clean Sidekiq metrics from multiproc dir on start | Aleksei Lipniagov | 2019-08-19 | 1 | -0/+51 |
| | | | | | | | 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 pid discovery for Unicorn in PidProvider | Aleksei Lipniagov | 2019-07-26 | 1 | -14/+52 |
| | |||||
* | Fix pid providing for Prometheus | Aleksei Lipniagov | 2019-07-18 | 1 | -0/+79 |
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. |