Zoom with a total bandwidth problem
Moderators: Developers, Moderators
Zoom with a total bandwidth problem
Hi,
When I zoom a graphic I have a total bandwidth number more bigger than it presents on the main graphic. Is it a feature or a bug?
When I zoom a graphic I have a total bandwidth number more bigger than it presents on the main graphic. Is it a feature or a bug?
I can report the same problem.
It happens too when displaying the four defined RRAs for a single graph, the total seems to be wrong on some graphs.
Apparently, I think that the total is not right on the graphs that partially span a period for which there is no value in the RRA.
Anyone can confirm this ?!
It happens too when displaying the four defined RRAs for a single graph, the total seems to be wrong on some graphs.
Apparently, I think that the total is not right on the graphs that partially span a period for which there is no value in the RRA.
Anyone can confirm this ?!
Same here, but i never considered it a bug, I think it's a feature ...
I think it's beacause of the average that is made on different time spans: 1MB/s will appear as such if you make one plot per second and such a flow lasts much more than one second, but if it lasts 10 seconds and you plot only each minute, you may have a spike at 167KB/s...
I'm right ?
I think it's beacause of the average that is made on different time spans: 1MB/s will appear as such if you make one plot per second and such a flow lasts much more than one second, but if it lasts 10 seconds and you plot only each minute, you may have a spike at 167KB/s...
I'm right ?
I agree with you on that point. But shouldn't the sum function take into account that (for ex.) 167KB/s was an average on 1 minute (167KB * 60s = approx. 10MB transferred) and 1MB/s was only during 10s (1MB * 10s = 10MB transferred too!) ?! I'm not sure this is a feature.nayco wrote:I think it's beacause of the average that is made on different time spans: 1MB/s will appear as such if you make one plot per second and such a flow lasts much more than one second, but if it lasts 10 seconds and you plot only each minute, you may have a spike at 167KB/s...
I think that spans on the main and zoomed graphics are equal.nayco wrote:I think it's beacause of the average that is made on different time spans: 1MB/s will appear as such if you make one plot per second and such a flow lasts much more than one second, but if it lasts 10 seconds and you plot only each minute, you may have a spike at 167KB/s...
You need rrdtool to install cacti. So I have rrdtool, of course.Hip wrote:Do you have the source (rrdtool command-line) used to generate these graphs ?! Maybe there some clue about the RRAs used or something like that.
How can I see, total bandwidth calculation is an internal function of the Cacti and it's result installs to the graph like a comment. I think that total bandwidth calculation may be realized with CDEF, but raX had reasons to create its own function. Zooming and sum are not working correctly together. We can try to analize this trouble or wait new release/patch/workaround.
I think you're right, you spot the problem.ilyassa wrote:"DEF call automatically chooses an RRA which contains CF consolidated data in a resolution appropriate for the size of the graph to be drawn." This is from the rrdtool manual. But bandwidth summarization uses resolution from the main graph (rra_id), isn't it?
The bandwidth_summation() function is given the $rra_steps based on the main graph. But when the rrdtool_function_fetch() function is called, it is just given a $start_time and $end_time.
Based on these two times (and as you quoted), rrdtool will internally select the RRA used to graph and/or to fetch the results. This works if the selected RRA is the same as the RRA used on the main graph.
BUT: if you zoom on a recent period, it is possible that the period covered by the zoom is fully available in a RRA with a smaller granularity. So this other RRA will be internally selected by rrdtool when fetching the values. Cacti will then multiply each value with the rra_steps of the original RRA, so the resulting traffic volume will be higher.
Does it make sense to you ?!
The "Resolution Interval" chapter in the rrdtool fetch manual provides the solution (to try !).
http://people.ee.ethz.ch/~oetiker/webto ... fetch.html
In brief: the start time and end time specified to rrdtool must be multiple of the resolution of the wanted RRA and the wanted RRA must cover the period (obvious).
I have no time to try this solution now but maybe tomorrow.
I quickly hacked a patch that adds resolution support when executing the rrdtool fetch command. This fixes the summation problem for me.
Can anyone (ilyassa ?) try this patch too and tell me the result ?!
Can anyone (ilyassa ?) try this patch too and tell me the result ?!
- Attachments
-
- cacti_sum_fix.patch.txt
- patch
- (2 KiB) Downloaded 406 times
Who is online
Users browsing this forum: No registered users and 0 guests