[cperciva]

other than the fact that the account balance alerts only consider storage used, not traffic charges. Grr.

I wish I had a good solution to this -- but it's impossible to predict when someone is going to be using lots of bandwidth, and alerting based on the current total spending rate had a very high false positive rate since bandwidth usage usually spikes for a single day and then goes down to a small fraction of the storage cost.

The downvoting is probably for being off-topic.

[Robin_Message]

Any discussion of the technology of someone who is running a small business is certainly on-topic.

So, what about using exponential smoothing or 95% peak estimation to get a better "current" spending rate? There is also the possibility to do some data mining on the actual usage (assuming you have collect that data and are willing to use it in aggregate to improve service) — i.e. customers who spend like you do and have a balance like yours usually run out of money after x days.

Another option I just thought of: try and estimate usage several different ways, and then check the variance — if its low, then issue an alert. I wouldn't be surprised if there is some research on how to do this, so it should be cook-up-able relatively easily if its a feature you want to add.

[cperciva]

Exponential smoothing and peak estimation won't help with the fundamental problem, which is that warning based on storage costs alone produces the correct result -- in the sense that funds run out after exactly 7 days -- 90% of the time. Any non-trivial addition of bandwidth costs into the equation is going to hurt far more often than it helps.

[diolpah]

Well, it doesn't produce the correct result for us, where bandwidth costs are more than 7 times storage costs, so we get our warning far too late.