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

Triggers based on Zabbix trapper items ignore specified evaluation periods

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Won't fix
    • Icon: Minor Minor
    • None
    • 2.4.7
    • Server (S)
    • None
    • Ubuntu 14.04, PostgreSQL 9.3+154ubuntu1. Using latest Zabbix 2.4.7 on all components (zabbix-server, zabbix-get) using Zabbix .deb packages from the Zabbix website.

      There seems to be an issue with Zabbix trapper items and time-based triggers. The specified evaluation period seems to be ignored and the trigger acts as if no evaluation period has been defined.

      Both the following triggers fail in the sense that they fire immediately without waiting for the specified delay time to pass:

      {Template_KNX:3_5_123.min(60)}=1
      

      Expected behaviour: Trigger should fire only if the item stays in the problem state (value '1' = problem) for more than 60 seconds.
      Actual behaviour: Trigger fires immediately as soon as the problem state is detected.

      Another example:

      ({TRIGGER.VALUE}=0 and {Template_KNX:3_5_124.last(0)}=1)
      or
      ({TRIGGER.VALUE}=1 and {Template_KNX:3_5_124.max(5m)}=0)
      

      Expected behaviour: Trigger should fire immediately and only be reset if the item returns to the normal state (0) for at least 5 minutes.
      Actual behaviour: Trigger gets reset immediately.

      STEPS TO REPRODUCE:

      1. Create an item with the following configuration:

      Name: Test
      Type: Zabbix trapper
      Key: test
      Type of information: Numeric (unsigned)
      Data type: Decimal
      [...the rest are default values...]
      

      2. Create a trigger with the following configuration:

      Name: Test trigger
      Expression: {Template_test:test.min(60)}=1
      [...the rest are default values...]
      

      3. Test the trigger:

      zabbix_sender -z zabbix_server -s hostname -k test -o 1
      

      Wait for a few seconds.

      Expected behaviour: Trigger will fire after 60 seconds.
      Actual behaviour: Trigger gets fired immediately.

            Unassigned Unassigned
            robert_m Robert Markula
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: