Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-22176

Undefined Macro isn't marked as Undefined when it should be

    XMLWordPrintable

Details

    • Incident report
    • Status: Open
    • Trivial
    • Resolution: Unresolved
    • 6.2.6
    • None
    • None
    • None
    • Ubuntu 20.04 (fully patched)

    Description

      Brief Synopsis: 

       

      Create a template with any name.

       

      Create an item (within the template) with the following key: net.if.in[\{$SNIFFERNICIP}]

       

      Create a trigger referencing the item (above) with the following information: 

      name: {HOST.NAME} - The Lansweeper Sniffer Interface may be having issues. Please investigate.

      expression: max(/BIC - Lansweeper Sniffer Network Interface/net.if.in[\{$SNIFFERNICIP}],30m)<"2000"

      Do not define the "SNIFFERNICIP" macro on the host or anywhere in the zabbix system.

       

      Expected outcome:  

      After some time, the trigger needs to be marked as 'undefined' and a reason needs to specify "Undefined Macro."  The trigger should not be placed into a 'problem' state.

       

      Actual outcome:  The trigger is NOT marked as 'undefined', however the trigger still goes into a problem state (reference screenshot)

      Attachments

        Activity

          People

            zalex_ua Oleksii Zagorskyi
            bradturnbough Brad Turnbough
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: