[ZBX-2918] inconsistent ordering Created: 2010 Aug 23  Updated: 2018 Sep 16  Resolved: 2018 Sep 16

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 1.8.3
Fix Version/s: None

Type: Incident report Priority: Minor
Reporter: Aleksandrs Saveljevs Assignee: Unassigned
Resolution: Won't fix Votes: 5
Labels: unsquashable, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File graph-list-1.png     PNG File graph-list-2.png     PNG File order-avg1-avg5.png     PNG File order-avg5-avg1.png    
Issue Links:
Duplicate
is duplicated by ZBX-4372 Description sort order wrong for item... Closed
is duplicated by ZBX-9231 Sort of items are incorrect Closed

 Description   

See order-avg5-avg1.png: avg5 comes before avg1. However, if we add an item with avg15, the ordering changes to avg15, avg1, and avg5: see order-avg1-avg5.png.

It should be noted that avg1, avg5, and avg15 in item description come from $3. However, a similar problem has been observed with graphs and there macros are not an issue.

 Comments   
Comment by richlv [ 2010 Aug 23 ]

positional references not being taken into account for sorting is a known issue : http://www.zabbix.com/documentation/1.8/manual/about/installation_and_upgrade#known_problems

i'm pretty sure there's an issue about that already as well, but i can't find it right now...

it was considered to be too resource intensive, so ordering of such entries is undefined (or more likely some id-dependent) currently.

what exact problem has been observed with graphs?

Comment by Aleksandrs Saveljevs [ 2010 Aug 23 ]

See graph-list-1.png and graph-list-2.png. Notice how the ordering of "Available memory" graphs depends on the name of the third graph.

Comment by richlv [ 2010 Sep 29 ]

hmm... with graphs it's just that they both have the same name, so i guess sorting is unspecified. maybe could be solved by adding secondary sort criteria on graph id

Comment by Alexander Vladishev [ 2018 Sep 16 ]

Positional macros became deprecated in version 4.0. I close this issue.

Generated at Thu Apr 25 11:59:47 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.