Cheshire Cat Computing

Is there any possibility that you can add (or show me how to add) a view to trend.cgi that will be based on "peak incoming traffic"?

Thanks!

This would require a small code change. The data retrieval currently pulls back the AVG consolidation faction - it would need to specify MAX instead.

If you feel up to hacking the code, just copy the trend.cgi module and make the change in the copy, then you can have two links - one for trending, one for max-trending.

Future versions I'll try and add this as a toggle option.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Thanks Steve, that worked perfect. Now is there any way to have the predictions not constrained by MaxBytes/AbsMax ?

Well, the code specifically constrains the predictions to AbsMax or MaxBytes because that is the behaviour of MRTG. It also calculates the time it expects the line to cross that boundary (or the zero line).

However, you can stop this. There is a test in the code that checks for zero or >{maxbytes} and sets the predicted value if so. You might end up with some weird graphs if you remove this, though - eg when the predicted line is too steep. It's there as a sanity check.

Is there any reason why you cant change the AbsMax or MaxBytes in your .cfg file? If these are really the hard limits of the value you are graphing, then why would you wantthe prediction line to go beyond them?

Look for this in the code:


The parts you need to remove are $curvala = $interfaces{$target}{maxbytes}; and $curvalb = $interfaces{$target}{maxbytes}; if you want to stop the prediction being capped at the max. I think you'll also need to remove the $$trenddelta[0]=0; and $$trenddelta[1]=0; if I remember rightly. This is being done from memory though...

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

We have several circuits that have a "flex" cap so we use MaxBytes to set that cap and then AbsMax to set the circuit max. An example is below, if there is a better way to do this then I would rather just do that then mess with your code



Thanks for your help!

Ah, I see your point.

Maybe I can fix the next version so that while it gives you the time index of crossing MaxBytes, its doesnt cap until AbsMax?

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11