Wouldn't it be simpler to either a) fix your services so they don't
have such a colourful failure mode, or b) if that's not possible
monitor the instantaneous traffic and alert or even shut things down
if it stays too high for too long?
Gordon
On Wed, 23 Feb 2022 at 08:50, Conrad Wood <cnw(a)conradwood.net> wrote:
Hi,
Sometimes some of my services misbehave in weird and wonderful ways.
If that happens, they can use an awful lot of bandwidth.
Whilst there is some monitoring that I can do (and do), I prefer to use
the data "closer to source".
There seems to be some data, that triggers pretty quickly and sends out
an email from "xfer a_t bitfolk.com" with the heading "Predicted to
exceed transfer quota".
However, rather than email I'd like an API, so that I can route it to
my alerting system. I do overlook emails sometimes, especially computer
generated ones.
My brain sometimes scans and classifies them too quickly as "deal with
it later" and incorrectly flags the email as 'not important'.
Having the information in my alerting system means I can route them so
that they remind me/trigger me again etc.
My questions are:
1. How often is that prediction calculated?
2. Is there an API I could query which gives me the data from the
email?
2.1 I'd settle for a binary API (predicted overusage == true|false)
2.2 otherwise an api that gives me the following values:
- predicted usage in
- contracted usage in
- predicted usage out
- contracted usage out
- Actual out
- Actual in
Nothing fancy required - a simple 'get' request or so would do just
fine ;)
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users