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

New values aren't counted towards trigger functions evaluation

    XMLWordPrintable

Details

    • Problem report
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 3.2.7rc1
    • 4.0.0alpha1, 4.0 (plan)
    • Server (S)
    • Zabbix 3.2.7rc1 (revision 68572)
    • Team A
    • Sprint 9, Sprint 10, Sprint 11, Sprint 12, Sprint 13, Sprint 14, Sprint 15, Sprint 16, Sprint 17, Sprint 18, Sprint 19, Sprint 20, Sprint 21, Sprint 23
    • 5

    Description

      Hello, team.
      I am observing very strange Zabbix behavior: for random amount of my 480000 items and 430000 triggers new values aren't triggering problem\ok trigger state change - if trigger got into Problem some time ago, new incoming value X = 0 for example with min(X)<1 won't switch trigger to Ok state.
      Situation can be fixed by going into item on host and clearing history\trends for it.
      One of the examples can be seen in attached screenshots. I'll be happy to give any kind of diagnostic information. Also I'll check generic 3.2.6 to see if bug repeats here.

      Attachments

        1. 2017-06-01_13-32-16.png
          2017-06-01_13-32-16.png
          96 kB
        2. 2017-06-01_14-50-31.png
          2017-06-01_14-50-31.png
          97 kB
        3. 2017-06-01_14-52-11.png
          2017-06-01_14-52-11.png
          27 kB
        4. 2017-06-01_14-52-53.png
          2017-06-01_14-52-53.png
          42 kB
        5. 2017-06-01_14-54-09.png
          2017-06-01_14-54-09.png
          154 kB
        6. 2017-06-01_14-58-03.png
          2017-06-01_14-58-03.png
          46 kB
        7. 2017-06-06_09-29-07.png
          2017-06-06_09-29-07.png
          40 kB
        8. 2017-06-06_09-31-13.png
          2017-06-06_09-31-13.png
          10 kB
        9. 2017-06-06_09-38-24.png
          2017-06-06_09-38-24.png
          70 kB
        10. query_fail_debug.patch
          0.7 kB
        11. reproduce.patch
          4 kB
        12. ZBX-12251_3.2.5_r67445_history_syncer_debug_info.txt
          6 kB
        13. ZBX-12251_3.2.6_r67849_history_syncer_debug_info.txt
          136 kB
        14. ZBX-12251-3.2.6.diff
          9 kB

        Issue Links

          depends on

          New Feature Request - A new feature request of the product, which has yet to be developed. ZBXNEXT-3006 A cache to provide multiple metrics of a single custom function

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is duplicated by

          Incident report - Incident report ZBX-10462 Trigger status stuck

          • Major - Major loss of function.
          • Closed

          Problem report - Problem report ZBX-11768 "cannot find open problem events for triggerid" message appears in zabbix_server.log after upgrade to 3.2.2

          • Major - Major loss of function.
          • Closed

          Problem report - Problem report ZBX-13776 Zabbix 3.4.4 doesn't resolve triggers

          • Major - Major loss of function.
          • Closed

          Incident report - Incident report ZBX-12859 False "More than 100 items having missing data for more than 10 minutes" alert

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          part of

          Problem report - Problem report ZBX-12179 Database errors can go unnoticed with DBselect(), DBfetch() functions

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Confirmed

          Activity

            People

              vso Vladislavs Sokurenko
              Paskal Dmitry Verkhoturov
              Votes:
              8 Vote for this issue
              Watchers:
              20 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: