How to avoid sending load alerts during backup timeframe?

This forum was archived to /woltlab and is now in read-only mode.
  • Hello,


    First of all, this is the first message I write on this forum so I hope I'm doing this the proper way.


    We're facing an annoying issue which I'm sure most of you already faced but I can't find a solution for it ;( .


    Every night we do run some backups on different hosts and pack them into tar.gz files, which increases the CPU usage considerably.


    Is there a way to do not raise any load average alert during a specific timeframe? Otherwise, we will be getting several alerts every night regarding the same issue.


    Thank you for your support!

  • Either you'll schedule a recurring downtime (an example is provided with the sample config). Or you'll raise/lower the thresholds based on a given time period. An example can be found over there in the documentation: http://docs.icinga.org/icinga2…ect-attributes-at-runtime (second example)

  • Either you'll schedule a recurring downtime (an example is provided with the sample config). Or you'll raise/lower the thresholds based on a given time period. An example can be found over there in the documentation: http://docs.icinga.org/icinga2…ect-attributes-at-runtime (second example)

    Danke Michael für deine Antwort!


    Actually, I do already have a downtime set on the affected hosts. However, there are still alerts being raised.


    Find below an example of the current configuration for the "load" service on one of the hosts:



    According to this, no alerts should be raised from 2h30 till 7h00, am I right?


    Thank you so much for your assistance, really appreciated!

  • Make sure that a Downtime is actually created upon that ScheduledDowntime definition (e.g. by querying the REST API endpoint /v1/objects/downtimes). The assign where expression based on the local host (NodeName) presumingly doesn't match for your other hosts.