[ZBX-2183] "unixtime" unit difference computed incorrectly Created: 2010 Mar 16  Updated: 2017 May 30  Resolved: 2012 Jun 29

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: None
Fix Version/s: 2.0.2rc1, 2.1.0

Type: Incident report Priority: Major
Reporter: richlv Assignee: Unassigned
Resolution: Fixed Votes: 1
Labels: latestdata, trivial, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBX-2424 change column in latest data Closed

 Description   

if an item has "unixtime" units, difference for 30 seconds is shown as follows :

+1970.01.01 03:00:31

so the diff is shown as unix time stamp in absolute, not relative time (and adding the timezone shift - that's where the 3 hours come from).

for unixtime & uptime units diff should be calculated as time between those timestamps instead



 Comments   
Comment by Ghozlane TOUMI [ 2011 Aug 12 ]

Actually the computation of difference for uptime is correct :
in the latest data, you can see +5m for 300secs update

The computation should be done using the same logic for unix timestamps...

Comment by Alexey Fukalov [ 2012 Jun 28 ]

dev branch: svn://svn.zabbix.com/branches/dev/ZBX-2183

For 'change; column in latest data, value is calculated same as for 'uptime' units, i.e. 'unixtime' units are overridden with 'uptime' when change is calculated.

Comment by Toms (Inactive) [ 2012 Jun 29 ]

(1) change has two "+" signs

<Vedmak> RESOLVED

<Toms> CLOSED

Comment by Toms (Inactive) [ 2012 Jun 29 ]

TESTED

Comment by Alexey Fukalov [ 2012 Jul 04 ]

Fixed in pre-2.0.2rc2 r28662, pre-2.1.0rc1 r28663

Generated at Sat Apr 27 03:35:51 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.