See www.zabbix.com for the official Zabbix site.

Docs/specs/ZBX-4344

From Zabbix.org
Jump to: navigation, search

Dependent event stuck in escalations

ZBX-4344

Status: v1.1

Owner: dimir

Summary

Current trigger dependency implementation is not complete. The dependencies are checked when a trigger changes its value (OK <-> PROBLEM) but not during the escalations. This may result in dependent trigger escalations continue being processed after a trigger it depends on fires.

Example

Imagine a monitored host that is behind a monitored router. A host has trigger T1 that depends on router trigger, T2. Here is an issue:

  1. host goes down, T1 fires
  2. T1 escalations are processed
  3. router goes down, T2 fires
  4. T2 escalations are processed
  5. T1 escalations continue being processed (this is a problem part)

Admin should stop receiving host availability problems when router goes down.

Solution

When escalations are processed the server should check if a dependent trigger has value PROBLEM. If such a trigger is found the escalations are freezed and considered again only after the dependent trigger gets value OK.

After the fix the above mentioned example should be processed as follows (consider that for both triggers the same action is configured):

  1. host goes down, T1 fires
  2. T1 escalation step 1 is processed
  3. router goes down, T2 fires
  4. T2 escalation step 1 is processed
  5. T2 escalation step 2 is processed
  6. T2 escalation step 3 is processed
  7. router goes up, T2 recovery
  8. the host is checked:
    1. if it's down T1 escalation step 2 is processed
    2. else T1 recovery

ChangeLog

  • 1.1 Change solution to freeze escalations instead of generating an OK event