Bug #6477

Sample bounds can jump around for custom timer periods on Status > Monitoring

Added by Jared Dillard about 2 years ago. Updated 18 days ago.

RRD Graphs
Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


Due to the way rrd_fetch tries to find the best fit for a time period, the custom time period can move around slightly from the desired start/end time, which can lead to missing sample points at the beginning or end.

Some further discussion on the issue can be found here:


#1 Updated by Chris Buechler about 2 years ago

  • Target version changed from 2.3.2 to 2.4.0
  • Affected Version changed from 2.3.1 to 2.3.x

#2 Updated by Renato Botelho 11 months ago

  • Target version changed from 2.4.0 to 2.4.1

#3 Updated by Jim Pingle 10 months ago

  • Target version changed from 2.4.1 to 2.4.2

#4 Updated by Jim Pingle 10 months ago

  • Target version changed from 2.4.2 to 2.4.3

#5 Updated by Jim Pingle 5 months ago

  • Target version changed from 2.4.3 to 2.4.4

#6 Updated by James Dekker about 1 month ago

On 2.4.4.a.20180707.0234 the does not appear to be an issue when viewing the Status > Monitoring graph at 1 hour time period, with resolution set to 1 minute. The first and last minute both appear to be represented accurately.

#7 Updated by Jim Pingle about 1 month ago

  • Status changed from New to Feedback

#8 Updated by James Dekker 29 days ago

On 2.4.4.a.20180720.1418, cannot reproduce. At one hour time period, with one minute resolution, the graph looks fine.

#9 Updated by Steve Beaver 18 days ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF