Source of maintenance.xliff - documentation

|*Daily*|Configure a daily maintenance period:&lt;br&gt;*Every day(s)* - maintenance frequency (1 - *(default)* every day, 2 - every two days, etc.);&lt;br&gt;*At (hour:minute)* - time of the day when maintenance starts;&lt;br&gt;*Maintenance period length* - for how long the maintenance will be active.&lt;br&gt;&lt;br&gt;When *Every day(s)* parameter is greater than "1", the starting day is the day that the *Active since* time falls on. Examples:&lt;br&gt;- if *Active since* is set to "2021-01-01 12:00", *Every day(s)* is set to "2", and *At (hour:minute)* is set to "23:00", then the first maintenance period will start on January 1 at 23:00, while the second maintenance period will start on January 3 at 23:00;&lt;br&gt;- if *Active since* is set to "2021-01-01 12:00", *Every day(s)* is set to "2", and *At (hour:minute)* is set to "01:00", then the first maintenance period will start on January 3 at 01:00, while the second maintenance period will start on January 5 at 01:00.|

<?xml version='1.0' encoding='UTF-8'?>

<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">

  <file source-language="en" target-language="nb-NO" datatype="plaintext" original="manual/maintenance.md">

    <body>

      <trans-unit id="c86bb2b9" xml:space="preserve">

        <source># 11 Maintenance</source>

      </trans-unit>

      <trans-unit id="e70ea305" xml:space="preserve">

        <source>#### Overview

You can define maintenance periods for hosts and host groups in Zabbix.

Furthermore, it is possible to define maintenance only for a single trigger (or subset of triggers) by specifying trigger tags.

In this case maintenance will be activated only for those triggers; all other triggers of the host or host group will not be in maintenance.

There are two maintenance types - with data collection and with no data

collection.

During a maintenance "with data collection" triggers are processed as

usual and events are created when required. However, problem escalations

are paused for hosts/triggers in maintenance, if the *Pause operations

for suppressed problems* option is checked in action configuration. In

this case, escalation steps that may include sending notifications or

remote commands will be ignored for as long as the maintenance period

lasts. Note that problem recovery and update operations are not

suppressed during maintenance, only escalations.

For example, if escalation steps are scheduled at 0, 30 and 60 minutes

after a problem start, and there is a half-hour long maintenance lasting

from 10 minutes to 40 minutes after a real problem arises, steps two and

three will be executed a half-hour later, or at 60 minutes and 90

minutes (providing the problem still exists). Similarly, if a problem

arises during the maintenance, the escalation will start after the

maintenance.

To receive problem notifications during the maintenance normally

(without delay), you have to uncheck the *Pause operations for

suppressed problems* option in action configuration.

::: noteclassic

If at least one host (used in the trigger expression) is not

in maintenance mode, Zabbix will send a problem

notification.

:::

Zabbix server must be running during maintenance. Maintenances are recalculated every minute or as soon as the configuration cache is reloaded if there are changes to the maintenance period.

Timer processes check if host status must be changed to/from maintenance at 0 seconds of every minute.

Additionally, every second the timer process checks if any maintenances must be started/stopped based on whether there are changes to the [maintenance periods] after the configuration update.

Thus the speed of starting/stopping maintenance periods depends on the configuration [update interval](/manual/appendix/config/zabbix_server#cacheupdatefrequency) (10 seconds by default).  Note that maintenance period changes do not include *Active since/Active till* settings. Also, if a host/host group is added to an existing active maintenance period, the changes will only be activated by the timer process at the start of next minute.

Note that when a host enters maintenance, Zabbix server

timer processes will read all open problems to check if it is required

to suppress those. This may have a performance impact if there are many

open problems. Zabbix server will also read all open problems upon

startup, even if there are no maintenances configured at the time.

Note that the Zabbix server (or proxy) always collects data regardless of the maintenance type

(including "no data" maintenance). The data is later ignored by the

server if 'no data collection' is set.

When "no data" maintenance ends, triggers using nodata() function will

not fire before the next check during the period they are checking.