graphite-dev team mailing list archive

[Kevin Blackham <question154372@xxxxxxxxxxxxxxxxxxxxx>]

Question #154372 on Graphite changed:
https://answers.launchpad.net/graphite/+question/154372

Kevin Blackham proposed the following answer:
1/60 gives you bytes per second if your dataset range is within the
259200 second bucket. You want to *8 for bits.  Scale 0.1333333.

When I get some time, I'll be adding a patch for auto determining the
scale factor based on the storage interval used for the source values.
For example, if you go beyond 259200 second range, you are now dipping
into 300 sec and scale is 0.0266667, and there is no way to know
automatically other than to notice your graph is totally out of whack.
:) (or fetch with &rawData=1 and the interval is in the leading columns
of the csv.)

On Apr 26, 2011, at 23:13, Matt Snow
<question154372@xxxxxxxxxxxxxxxxxxxxx> wrote:

> Question #154372 on Graphite changed:
> https://answers.launchpad.net/graphite/+question/154372
> 
> Matt Snow posted a new comment:
> Thanks Jason. I use the nonNegativeDerivative() but i'm fairly certain
> the byte counters in the Linux kernel do not roll over. there are
> actually a lot of gripes about this from Solaris admins since you can
> reset the network interface counters in Solaris.
> 
> I guess I didn't really think about it much as for how to get the
> numbers looking how I want them.
> 
> The storage retention for my network data is
> 60:259200,300:103680,3600:8760. Each metric sample is collected every 60
> seconds and sent to graphite. so if 1 / 60 is 0.0166 then that should be
> my scale, correct?
> 
> -- 
> You received this question notification because you are a member of
> graphite-dev, which is an answer contact for Graphite.
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~graphite-dev
> Post to     : graphite-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~graphite-dev
> More help   : https://help.launchpad.net/ListHelp

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.