last value gotten via zabbix_sender with timestamp in wrong oder

XMLWordPrintable

    • Type: Problem report
    • Resolution: Won't fix
    • Priority: Trivial
    • None
    • Affects Version/s: 6.2.4
    • Component/s: None
    • None

      Steps to reproduce:

      1. Create a zabbix trapper item float
      2. Set a trigger on trapper item last(//trapperitem)>0
      3. send 2 values via zabbix_sender with timestamp in diffenerent order
      4. "TEST" trapperitem 1668167005 0 (timestamp=now)
      5. "TEST" trapperitem 1668166866{1 (timestamp=old){}
      6. Check Alerts

      Result:
      Alert rises. But on latest Data the order is the right one.
      Expected:
      No Alerts. The latest Value should be 0 because of the order via timestamp parameter. 

            Assignee:
            Karlis Salins (Inactive)
            Reporter:
            S K
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: