[ZBX-16449] Wrong order of the displayed latest values in problems Created: 2019 Aug 01  Updated: 2024 Apr 10  Resolved: 2019 Sep 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 4.0.11, 4.2.5
Fix Version/s: 4.0.13rc1, 4.2.7rc1, 4.4.0alpha3, 4.4 (plan)

Type: Problem report Priority: Minor
Reporter: Aleksejs Sestakovs Assignee: Vasily Goncharenko (Inactive)
Resolution: Fixed Votes: 0
Labels: lastvalue, order
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File items.png     PNG File problems.png     PNG File triggers.png    
Team: Team D
Sprint: Sprint 55 (Aug 2019)
Story Points: 0.25

 Description   

Steps to reproduce:

  1. Create two triggers and corresponding trapper items (see attached items.png and triggers.png).
    Note that trigger_02 is the same as trigger_01 but with the additional condition and different function in the end of expression.
  2. Fire the triggers by sending the following values for the items
    ./bin/zabbix_sender -z 127.0.0.1 -s "Zabbix server" -k trap_key_01 -o 5
    ./bin/zabbix_sender -z 127.0.0.1 -s "Zabbix server" -k trap_key_02 -o 7

Result:
The order of the displayed latest values in Monitoring->Problems view is wrong for trigger_02. See problems.png attached.
Expected:
The latest values should be displayed in the same order as items are written in the trigger expression. In this particular test case the order of the latest values should be the same for both problems.



 Comments   
Comment by Vasily Goncharenko (Inactive) [ 2019 Aug 29 ]

Fixed in:

  • 4.0.13rc1 eb3d4b9400a
  • 4.2.7rc1 0b01bcd7940
  • 4.4.0alpha3 (master) f6b9252ae39
Generated at Wed Apr 24 05:31:16 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.