<p>I'm using the official <a href="https://github.com/helm/charts/tree/master/stable/prometheus-operator" rel="noreferrer">stable/prometheus-operator</a> chart do deploy Prometheus with helm.</p>

<p>It's working good so far, except for the  annoying <code>CPUThrottlingHigh</code> alert that is firing for many pods (including the own Prometheus' <a href="https://github.com/coreos/prometheus-operator/issues/2171" rel="noreferrer">config-reloaders containers</a>). This alert is <a href="https://github.com/kubernetes-monitoring/kubernetes-mixin/issues/108" rel="noreferrer">currently under discussion</a>,  and I want to silence its notifications for now.</p>

<p>The Alertmanager has a <a href="https://prometheus.io/docs/alerting/alertmanager/#silences" rel="noreferrer">silence feature</a>, but it is web-based:</p>

<blockquote>
  <p>Silences are a straightforward way to simply mute alerts for a given
  time. Silences are configured in the web interface of the
  Alertmanager.</p>
</blockquote>

<p><strong>There is a way to mute notifications from <code>CPUThrottlingHigh</code> using a config file?</strong></p>

Eduardo Baitello
<p>One option is to route alerts you want silenced to a "null" receiver. In <code>alertmanager.yaml</code>:</p>

<pre><code>route:
  # Other settings...
  group_wait: 0s
  group_interval: 1m
  repeat_interval: 1h

  # Default receiver.
  receiver: "null"

  routes:
  # continue defaults to false, so the first match will end routing.
  - match:
      # This was previously named DeadMansSwitch
      alertname: Watchdog
    receiver: "null"
  - match:
      alertname: CPUThrottlingHigh
    receiver: "null"
  - receiver: "regular_alert_receiver"

receivers:
  - name: "null"
  - name: regular_alert_receiver
    &lt;snip&gt;
</code></pre>
