概述

    实际应用中,这意味着:

    • 用户可以立即收到新问题通知

    • 通知可以重复,直到问题解决

    • 发送通知可以延时

    • 通知可以升级到另一个“较高”的用户组

    • 可以立即执行远程命令,或者长时间不解决问题

    操作会根据升级步骤进行升级。 每一步都有一段时间.

    您可以定义默认持续时间和单个步骤的自定义持续时间。一个升级步骤的最短持续时间为60秒。

    您可以从任何步骤开始执行操作,例如发送通知或执行命令。 第一步是立即采取行动。 如果要延迟操作,可以将其分配给稍后的步骤。 对于每个步骤,可以定义几个操作。

    升级步骤的数量不受限制。

    配置操作是即可定义Escalations. Escalations仅对问题操作支持,而不是恢复.

    Escalations的其他方面

    让我们考虑如果一个操作包含几个升级步骤,在不同的情况下会发生什么。

    Escalation 示例

    示例 e 1

    Sending a repeated notification once every 30 minutes (5 times in total) to a 'MySQL Administrators' group. To configure:

    • Set the escalation steps to be From '1' To '5'

    • Select the 'MySQL Administrators' group as recipients of the message

    Notifications will be sent at 0:00, 0:30, 1:00, 1:30, 2:00 hours after the problem starts (unless, of course, the problem is resolved sooner).

    If the problem is resolved and a recovery message is configured, it will be sent to those who received at least one problem message within this escalation scenario.

    If the trigger that generated an active escalation is disabled, Zabbix sends an informative message about it to all those that have already received notifications.

    示例 2

    Sending a delayed notification about a long-standing problem. To configure:

    • In Operations tab, set the Default operation step duration to '36000' seconds (10 hours)

    • Set the escalation steps to be From '2' To '2'

    4 Escalations - 图2

    A notification will only be sent at Step 2 of the escalation scenario, or 10 hours after the problem starts.

    You can customize the message text to something like 'The problem is more than 10 hours old'.

    示例 3

    Escalating the problem to the Boss.

    Note the use of {ESC.HISTORY} macro in the message. The macro will contain information about all previously executed steps on this escalation, such as notifications sent and commands executed.

    示例 4

    A more complex scenario. After multiple messages to MySQL administrators and escalation to the manager, Zabbix will try to restart the MySQL database. It will happen if the problem exists for 2:30 hours and it hasn't been acknowledged.

    If the problem still exists, after another 30 minutes Zabbix will send a message to all guest users.

    If this does not help, after another hour Zabbix will reboot server with the MySQL database (second remote command) using IPMI commands.

    4 Escalations - 图4

    示例 5

    An escalation with several operations assigned to one step and custom intervals used. The default operation step duration is 30 minutes.

    通知将发送如下:

    • to MySQL administrators at 0:00, 0:30, 1:00, 1:30 after the problem starts

    • to Database manager at 2:00 and 2:10 (and not at 3:00; seeing that steps 5 and 6 overlap with the next operation, the shorter custom step duration of 600 seconds in the next operation overrides the longer step duration of 3600 seconds tried to set here)

    • to guest users at 4:00 hours after the problem start (the default step duration of 30 minutes returning between steps 8 and 11)