[ZBX-8197] Cannot view all data for a history graph Created: 2014 May 12 Updated: 2017 May 30 Resolved: 2014 Jun 02 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | 2.2.4rc1 |
Fix Version/s: | 2.3.2 |
Type: | Incident report | Priority: | Major |
Reporter: | Pavels Jelisejevs (Inactive) | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | frontend, graph, timeperiodselection | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
When I open a chart for an item with some data, the graph is displayed correctly. I can set the period for almost two years (~1y 11m 29d) and the graph is still displayed correctly. But, when I press "All" and the period is set to 2 years, the graph is rendered empty. For some reason, after pressing "All" the "stime" parameter of the graph URL is set to "20010401220359". This value is also remembered in the profiles table and opening the latest data page again sets the timebar to year 2001. The broken graph URL looks like this: /chart.php?itemid=26452&period=63072000&stime=20010401220359&updateProfile=1&profileIdx=web.item.graph&profileIdx2=26452&sid=7d887b55052a47b3&width=1087&curtime=1399891905821 |
Comments |
Comment by Krists Krigers (Inactive) [ 2014 Jun 02 ] |
Resolved in r46085, branch svn://svn.zabbix.com/branches/dev/ZBX-8197. |
Comment by Oleg Egorov (Inactive) [ 2014 Jun 12 ] |
(1) No string changes |
Comment by Oleg Egorov (Inactive) [ 2014 Jun 12 ] |
TESTED |
Comment by richlv [ 2014 Jun 12 ] |
(2) could you please add info on what caused this ? kristsk For some reason there was a condition that in case period was bigger than timeline.maxperiod, reset slider (and stime parameter for chart image request) to be from far past. RESOLVED. <richlv> thanks. i'm slightly afraid of potential edge cases this was supposed to cover, but let's hope there were none by now - CLOSED |
Comment by Krists Krigers (Inactive) [ 2014 Jun 13 ] |
Fixed and merged to 2.3.2 (trunk) in r46483. |