On Mon, May 23, 2005 at 10:31:30AM +1200, Simon Byrnand wrote:
> However one comment - reading byte counters from TC (assuming thats what it
> does - I havn't studied it or installed it yet) for the purposes of billing
> customer usage is not recommended, as the HTB docs specifically say that
> they are not completely accurate due to rounding. (And we have also found
> they are a bit inaccurate)
Sure, it's not for billing. But one can analyze HTB "feeling and
behaviour" with these scripts anyway. It's great if I can tell my customer
something like "yes, right you are, you are experiencing delays (up to 10
seconds BTW), and that's because your bandwidth exhausted; no, no, no
drops, just delaying..."
:-)
> Then in mrtg.cfg:
>
> Target[CustomerName]: `/root/mrtg/bin/get-radiolink-use`
>
> This is a simplified example that doesn't take into account more than one
> customer. To scale up you would want the various scripts to be
> automatically generated...
>
> We find byte counting using ipchains/iptables to be very accurate, and no
> SNMP is needed provided the byte counting is done on the same machine as
> mrtg is run...
Once more: mrtg can deal with rrd bases, I believe you assume such setup,
dont you?-)
You can store rrd bases regularly and fetch the data with scripts.
ps. I like rrd bases and work with them directly very often, with no mrtg.
As you can see :-) That's why py-htbstat uses py-rrdtool.
>
> Regards,
> Simon
--
_,-=._ /|_/|
`-.} `=._,.-=-._., @ @._,
`._ _,-. ) _,.-'
` G.m-"^m`m' Dmytro O. Redchuk
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
