Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-9412

scope: notice missing on Cluster node [{#NODE.NAME}]: Status changed trigger

XMLWordPrintable

    • Icon: New Feature Request New Feature Request
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 7.0.2, 7.2.0alpha1
    • Templates (T)

      I am reporting missing tag scope:notice in
      Templates Zabbix server health > Discovery rule High availability cluster node discovery > Trigger prototype Cluster node [

      {#NODE.NAME}

      ]: Status changed .

      I see "scope: notice" on trigger means it not problem, but just something that occured and there is not meaningful "resolution" of that event. So I create two trigger action rules using this concept. One rule that report "Problem" and "Resolved" if no scope:notice tag and separate rule that report "Event" if scope:notice tag exists.

      Missing tag than causes confusion when trigger action reports "Cluster node status change was Resolved" for (long forgotten) failover that happened 12h ago which is side-effect of Discard unchanged with heartbeat on zabbix.node.status item.

      PS: Discard unchanged with heartbeat also hides failovers when they happen sooner than 12h after previous. Is that intended? I suggest PROBLEM event generation mode Multiple so zabbix reports all failovers properly.

            abakaldin Alexander Bakaldin
            user185953 user185953
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: