[ZBX-18178] Latest data opens too long Created: 2020 Aug 01  Updated: 2020 Aug 06  Resolved: 2020 Aug 06

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

Type: Problem report Priority: Major
Reporter: Vekli Sergey Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 20.04


Attachments: PNG File image-2020-08-01-17-41-31-196.png    
Issue Links:
Duplicate
duplicates ZBX-18071 'Latest data' timeout via Monitoring ... Closed

 Description   

No steps fro reproduce, just default installation.

Result:

Postgresql logs looks like this:

 2020-08-01 02:11:09.112 MSK [145977] zabbix@zabbixdb СООБЩЕНИЕ: продолжительность: 540792.778 мс, оператор: SELECT itemid FROM history_uint WHERE itemid IN
 (110564,110565,110566,110567,110568,110569,110570,110571,110572,110573,110574,110575,110576,110577,110578,110579,110580,110581,110582,110583,110584,110585,11
 0586,110587,110588,110589,110590,110591,110592,110593,110594,110595,110596,110597,110598,110599,110600,110601,110602,110603,110604,110605,110606,110607,11060
 8,110609,110610,110611,110612,110613,110614,110615,110616,110617,110618,110619,110620,110621,110622,110623,110624,110625,110626,110627,110628,110629,110630,1
 10631,110632,110633,110634,110635,110636,110637,110638) GROUP BY itemid HAVING MAX(clock)>1596150128


 Comments   
Comment by Vekli Sergey [ 2020 Aug 01 ]

**Problem was fixed by changing include/classes/api/managers/CHistoryManager.php

Line 76: ' WHERE '.dbConditionInt('itemid', $type_itemids).($period ? ' AND clock>'.$period : '').

 

Comment by Valdis Murzins [ 2020 Aug 06 ]

Thank you, [email protected] for the report and suggestion.
This improvement is already implemented in ZBX-18071.

With this I am closing this issue as DUPLICATE of ZBX-18071.

Generated at Thu Apr 03 09:20:11 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.