<p>When nodes reboot based on the job &quot;kured_reboots&quot;, alertManager still alerts on other node alerts. Is there a way to stop alertManager alerts for nodes going through a reboot based on the job &quot;kured_reboot'? Something like this:</p>
<pre><code>route:
  receiver: default
  group_by:
  - cluster
  - namespace
  - severity
  - alertname
  - job
  continue: false
  routes:
  - receiver: receiver1
    matchers:
    - job =~ &quot;kured_reboot&quot;
    active_time_intervals:
    - business-hours
  inhibit_rules:
  - source_matchers:
  - job=&quot;kured_reboot&quot;
  target_matchers:
  - severity=~&quot;critical|warning|info&quot;
  equal:
  - namespace
  - alertname
</code></pre>
<p>So far, I am still researching this and have not tried anything yet. I wanted to ask if anyone has done something like this before.</p>

<p>Generally there are two way to do it:</p>
<ol>
<li><p>Incorporate additional check about this job into your alert rules. For this you'll need to add something like <code>unless on() my_job_status{name=&quot;kured_reboot&quot;} == 1</code> (You might need to something similar or even completely different depending on your situation and style of job and metrics related to it)</p>
</li>
<li><p>Create alert based on the fact that this job is running and add the <a href="https://prometheus.io/docs/alerting/latest/configuration/#inhibit_rule" rel="nofollow noreferrer">inhibition rule</a>, that will prevent other alert from firing while job is running.</p>
</li>
</ol>
