Aggregate plugin - How to graph total traffic?

[lfcarneiro]

Hello, all.

Here at RNP, we are using 0.8.7b Cacti version, 2,1 Plugin Architecture version and 0.66 Aggregate plugin version. Our basic problem is the following: if we want to graph the traffic measured in more than one physical data interface, as E1 interfaces for instance, Aggregate plugin only graphs traffics of each interface separately, as you can see in the picture attached.

Our doubt is: is there anyone who graphed total traffic of a physical trunk as it was only one interface?

Any suggestions are extremely welcome.

Thanks in advance and best regards,

[gandalf]

Request for Discussion!

There are several approaches, not all of them involving AGGREGATE

1. Extending AGGREGATE
The most wanted add on is to automatically ADD a total gprint line in the legend. It's on my todo but no date set.

2. AGGREGATE with TOTAL ONLY
Not yet on my todo. Would work like:
- Select all interfaces to be aggregated as usual
- DO NOT graph each base item but
- Graph and GPRINT the total only

3. non-AGGREGATE option
I recently created a quite generic data input method. Here's how it works:
- It fetches a base OID, let's say the base OID for the ifInOctets (Traffic In)
- it then snmpwalks this OID, adding up all items that return data
- it stores this SUM into rrd and graphs it
Advantage: No aggregate required. Autmatically adds all new interfaces without user interaction
Disadvantage: Always collects ALL interfaces related to some base OID. If only a "selected list of interfaces" is required, this will fail.


I happily accept discussion on this topic.
But do NOT assume that discussion will automatically lead to implementation. I have to feed my family like you do
Reinhard

[lfcarneiro]

Hello, Reinhard.

The third approach might be interesting. Could you pass this generic data input method here in the post? I would like to test it.

Regards,

[gandalf]

Well, I don't have it on my local system. And no documentation yet. So please be prepared to fight a bit on your own. I'll try to post it tomorrow or on friday
Reinhard

[Howie]

Request for Discussion!

There are several approaches, not all of them involving AGGREGATE

1. Extending AGGREGATE
The most wanted add on is to automatically ADD a total gprint line in the legend. It's on my todo but no date set.

Having it automatically group together the similar-named items would be helpful too - for the classic '+ve stack/-ve stack' aggregate graph, anyway. Separating out the traffic_in's from the traffic_out's is the main reason I don't bother with more aggregate graphs.

[gandalf]

Request for Discussion!

There are several approaches, not all of them involving AGGREGATE

1. Extending AGGREGATE
The most wanted add on is to automatically ADD a total gprint line in the legend. It's on my todo but no date set.

Having it automatically group together the similar-named items would be helpful too - for the classic '+ve stack/-ve stack' aggregate graph, anyway. Separating out the traffic_in's from the traffic_out's is the main reason I don't bother with more aggregate graphs.

Sure, it will use SIMILAR_DATA_SOURCES_NODUPS ...
Reinhard

[Howie]

Request for Discussion!

There are several approaches, not all of them involving AGGREGATE

1. Extending AGGREGATE
The most wanted add on is to automatically ADD a total gprint line in the legend. It's on my todo but no date set.

Having it automatically group together the similar-named items would be helpful too - for the classic '+ve stack/-ve stack' aggregate graph, anyway. Separating out the traffic_in's from the traffic_out's is the main reason I don't bother with more aggregate graphs.

Sure, it will use SIMILAR_DATA_SOURCES_NODUPS ...
Reinhard

I meant for the original aggregate stack, not the total. Not really on-topic, sorry.

[lfcarneiro]

Hello, Reinhard.

In relation to your generic data input method, we are with a doubt: If I have a router with six network interfaces, for instance, and I only want to graph traffic of four of them, this data input method is not going to work, is it?

Thanks and best regards,

[gandalf]

Well, I don't have it on my local system. And no documentation yet. So please be prepared to fight a bit on your own. I'll try to post it tomorrow or on friday
Reinhard

I was under the impression to discuss this on 3.CCC.eu, but we did not cover this topic. I was hoping for more ideas so I will post it the way it works now sometime this week.
Reinhard

[gandalf]

Hello, Reinhard.

In relation to your generic data input method, we are with a doubt: If I have a router with six network interfaces, for instance, and I only want to graph traffic of four of them, this data input method is not going to work, is it?

Thanks and best regards,

Hah, this might be the first improvement to the not-yet-published script. Are you able to define an abstract representation of "the correct 4 interfaces"? Would a regexp help when being applied to the base OID?
Reinhard

[lfcarneiro]

Hi, Reinhard.

Unfortunately, I am not able to define this abstract representation of "the correct 4 interfaces". I am only a simple networks engineer, not a great and famous developer...

Anyway, I am waiting for your script, even with this problem. I don't remeber if it is already mentioned before, but are 0.8.8 Cacti version going to fix this problem with aggregate traffic's legends? Or the new Plugin Architecture version?

Thanks and regards,

[gandalf]

Hi, Reinhard.

Unfortunately, I am not able to define this abstract representation of "the correct 4 interfaces". I am only a simple networks engineer, not a great and famous developer...

I'm thinking of a regexp here. Hoping to solve most issues. But will still require some development.

Anyway, I am waiting for your script, even with this problem. I don't remeber if it is already mentioned before, but are 0.8.8 Cacti version going to fix this problem with aggregate traffic's legends? Or the new Plugin Architecture version?

What problem do you refer to? Either I'm drunk (which would not be as unusual just after a party) or my brain's long time memory was just swapped out.
Reinhard

[yuval_ba]

In reply to gandalf discussion request:

I am also in need to aggregate multiple traffic graphs and find it hard with current AGGREGATE features.

this is quite a common need for us (and I'm sure for many others) to select several interfaces and create aggregate traffic graph. I tend to keep such interfaces with common ifAlias that can easily be matched via regexp, so this will be very handy. but it's still possible to do via the Graph Managment interface today.

option 2 sounds good because it will give the desired graph, but the disadvantage is that the graph will not contain per interface LEGEND info.

I did manage to create my graph by using AGGREGATE on 4 interfaces. and then manually re-ordering the traffic_in and traffic_out in 2 groups and then changing traffic_in's to AREA/STACK and traffic_out's to LINE1 and hiding all except the last one. of course it is not very do-able for larger num of interfaces.

options 3 does not sound very good to me because:
if you decide to add new interface to the aggregate even if you already have data for it, it will only add from that time point to the dedicated rrd, and you will not be able to use the existing history (hope I'm clear enough).