An action condition "Time period" could resolve your requirements.

As for the very last sentence - there is a separate feature request ZBXNEXT-413.

"Time period" is indeed one of the possible approaches, but it seems that it is not enough in the general case (like school holidays in the example).

Thanks oleksiy. I have used the time period condition when I expect something to only occur within a weekly basis. Sometimes you need to specify actions to be disabled on a fortnightly or monthly basis of for start to end periods like holidays etc...

I have viewed previous requests for individual trigger maintenance and as mentioned this would somewhat allow for suppressing any output from the individual trigger firing as a side effect (depending on action configuration).

We need something like this, too. The actions normally should be started out of the working hours which are actually configured using time periods. This works good. But if there is a holiday it should be started the whole day. So within the action condition we need a possibility to check if the day is a local holiday. I could imagine the following solutions:

• Configuration of holidays and similar days.
  • With this you can add dates or date ranges and define it as holiday. A more flexible way is use categories and one of them would be "holiday".
  • Then within the action condition there could be something like this:

    Holiday=True

    or

    DayCategory="holiday"

• Configure a script within the AlertScriptsPath.
  • Zabbix will execute the script with the event's timestamp and optionally additional parameters (for example a day category) and compare the script's return value.

Maybe ZBXNEXT-537 would be a suitable solution.