Commit 0d915d61 authored by Jacob Vosmaer's avatar Jacob Vosmaer

Unmonitor after too many sidekiq restarts

For monit, unmonitoring means giving up.
parent 39ae29cc
...@@ -10,7 +10,7 @@ check process gitlab_sidekiq with pidfile <%= @sidekiq_pid_path %> ...@@ -10,7 +10,7 @@ check process gitlab_sidekiq with pidfile <%= @sidekiq_pid_path %>
# Assuming our server has two cores, 40% totalcpu means pinning 80% of a single core # Assuming our server has two cores, 40% totalcpu means pinning 80% of a single core
if totalcpu is greater than <%= @cpu_threshold %>% for <%= @cpu_cycles_number %> cycles then restart if totalcpu is greater than <%= @cpu_threshold %>% for <%= @cpu_cycles_number %> cycles then restart
if totalmem is greater than <%= @mem_threshold %> MB for <%= @mem_cycles_number %> cycles then restart if totalmem is greater than <%= @mem_threshold %> MB for <%= @mem_cycles_number %> cycles then restart
if <%= @restart_number %> restart within <%= @restart_cycles_number %> cycles then alert if <%= @restart_number %> restart within <%= @restart_cycles_number %> cycles then unmonitor
group gitlab_sidekiq group gitlab_sidekiq
check program sidekiq_load_ok with path "/usr/local/bin/sidekiq_load_ok" check program sidekiq_load_ok with path "/usr/local/bin/sidekiq_load_ok"
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment