GitLab Bot
31522c5182
Add latest changes from gitlab-org/gitlab@master
2022-08-18 09:11:27 +00:00
GitLab Bot
c17eb7c970
Add latest changes from gitlab-org/gitlab@master
2022-01-20 15:11:58 +00:00
GitLab Bot
34ad6d995b
Add latest changes from gitlab-org/gitlab@master
2021-05-21 09:10:16 +00:00
GitLab Bot
e5e0589e09
Add latest changes from gitlab-org/gitlab@master
2021-04-26 12:09:44 +00:00
GitLab Bot
9ecdb93f4e
Add latest changes from gitlab-org/gitlab@master
2021-02-01 12:09:03 +00:00
GitLab Bot
c59765a50a
Add latest changes from gitlab-org/gitlab@master
2020-06-24 18:09:03 +00:00
GitLab Bot
0e54270ecf
Add latest changes from gitlab-org/gitlab@master
2020-05-21 12:08:08 +00:00
GitLab Bot
90a06a20be
Add latest changes from gitlab-org/gitlab@master
2019-11-07 15:06:33 +00:00
GitLab Bot
b539ac1d61
Add latest changes from gitlab-org/gitlab@master
2019-10-30 09:27:58 +00:00
GitLab Bot
184c2ced07
Add latest changes from gitlab-org/gitlab@master
2019-10-17 18:08:05 +00:00
GitLab Bot
00c78fb814
Add latest changes from gitlab-org/gitlab@master
2019-10-16 15:06:17 +00:00
Aleksei Lipniagov
35fb27db27
Remove worker label from puma terminations metric
2019-08-12 13:52:15 +03:00
Jan Provaznik
13364c00d5
Monitor only final states
...
There is no reason to monitor transition states so we ignore
ready and active states. We can get ratio of completed vs failed
requests from final states.
2019-06-12 12:33:34 +02:00
Jan Provaznik
d3a7bdda98
Moved RackTimeout observer to a different location
...
Because there will be similar observer for PumaWorkerKiller,
it makes sense to keep both on better place.
2019-06-12 12:09:04 +02:00
Jan Provaznik
497acb1670
Add metric for measuring PumaWorkerKiller activity
...
PumaWorkerKiller is used for periodically checking and killing
workers (the biggest one) if overall memory reaches specified
limit. This metric allows us to watch number of killed workers.
2019-06-10 16:09:40 +00:00
