Aggregate graph totals not adding correctly

[NeilAgg]

For some reason, when I create an aggregate graph, the numbers are not looking like they add up.

Take a look at the attached graph.

The Inbound Max and Outbound Max are the same number. That should not be the case.

Also, the 95th percentile for the total traffic in+out is 0.85 mbit, but the total like is clearly higher than that. As a matter of fact, that is the 95th percentile for the first data set.

I read the manual, but it does not seem to help.

Any ideas what went wrong?

[NeilAgg]

I think I figured something out: I needed to total similar data sources and not all data sources. The manual text is a bit cryptic so I was not understanding the difference.

Now, the inbound and outbound totals look like they are calculating correctly.

But, the 95th percentile is still the same as the one for the first data set which seems unlikely to me.

Any ideas?

[gandalf]

I think I figured something out: I needed to total similar data sources and not all data sources. The manual text is a bit cryptic so I was not understanding the difference.

I will accept any improvement to the documentation. Simply drop me your text.

But, the 95th percentile is still the same as the one for the first data set which seems unlikely to me.

Please visit the graph at Graph Management and DEBUG to see, what the 95th percentile does exactly. If I'm not mistaken, AGGREGATE won't treat the 95th percentile at all.

Reinhard

[NeilAgg]

I will accept any improvement to the documentation. Simply drop me your text.

The confusion I ran into was using the term data source. In the data sources management screen, each port on my switch is listed once. But, the total similar data sources aggregated the inbound traffic and outbound traffic separately. So, the naming is not consistent. On the data sources page, a port is a data source but on the aggregate configuration, a port seems to be two data sources.

Changing the labels to:
Total all traffic
Total inbound and outboud traffic separately
would be extremely clear, but may not apply to non-traffic data sources.

If I'm not mistaken, AGGREGATE won't treat the 95th percentile at all.

Actually, I found a solution to this and posted it in a separate post:
http://forums.cacti.net/viewtopic.php?t=33435