-
Type:
Incident report
-
Resolution: Duplicate
-
Priority:
Trivial
-
None
-
Affects Version/s: 3.0.20, 3.4.12
-
Component/s: Frontend (F)
-
None
There is a difference between the screen source and SQL sort of trigger status.
When it exceeds SQL LIMIT, it becomes a list which lost of lastchange data.
I think that sorting in descending order on the SQL side should take precedence.
Trigger data list query(ASC):
MariaDB [zabbix]> SELECT DISTINCT t.triggerid,t.lastchange FROM triggers t,functions f,items i WHERE i.hostid='10084' AND f.triggerid=t.triggerid AND f.itemid=i.itemid AND NOT EXISTS (SELECT NULL FROM functions f,items i,hosts h WHERE t.triggerid=f.triggerid AND f.itemid=i.itemid AND i.hostid=h.hostid AND (i.status<>0 OR h.status<>0)) AND t.status=0 AND t.flags IN ('0','4') ORDER BY t.lastchange LIMIT 22;
Trigger lists image(DESC):
thank you.
- duplicates
-
ZBXNEXT-4896 Re-execute SQL query when resorting problems
-
- Open
-