Bug #1990

Custom RRD Graphs Does NOT Properly Graph "End" Value

Added by Simon Fong about 9 years ago. Updated about 9 years ago.

Web Interface
Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


When I try to Set a "Start" value in Unix time AND an "End" value in Unix time, the "End" value turns into current Unix time.

I wish to select a specific time period in order to determine how much data I've used. This is particularly important for those with monthly caps.

Associated revisions

Revision 0d5f874d (diff)
Added by Seth Mos about 9 years ago

Actually reflect the end time instead of always $now.
Fix Ticket #1990


#1 Updated by Chris Buechler about 9 years ago

  • Assignee deleted (Simon Fong)
  • Priority changed from High to Normal
  • Target version deleted (2.0.1)

#2 Updated by Seth Mos about 9 years ago

  • Status changed from New to Feedback

Found the cause, we were using $now instead of $end, this should resolve it.

Do take note that there is a 5 second hold down timer in the graphing script to prevent a denial of service.

#3 Updated by Simon Fong about 9 years ago

Thank you Seth for fixing this issue!!

If only I can input dates & times on the "Custom RRD Graphs" page in human readable form (not Unix time), then it'll be perfect. Online Unix time converters were never able to get the time zones correct or compensate for daylight-saving. I had to use a MS Excel spreadsheet I created to make the conversions to/from Unix time.

#4 Updated by Seth Mos about 9 years ago

It was on the todo list but forgotten, I am not sufficiently at home in javascript to do the calendar thing.

#5 Updated by Seth Mos about 9 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF