Device dependencies would be a lovely addition for us.

We monitor a lot of small customer sites, generally behind a single router.
If their broadband goes down, we then get a load of notifications because we're unable to poll anything behind it.
In this situation, its only the broadband being down which really warrants an alert - everything else is caused by it.

Regards,
James Tandy
TandyUK Servers Limited

Tel: 01903 247 011
Www: http://www.tandyukservers.co.uk
Email: support@tandyukservers.co.uk

TandyUK Servers Limited Registered in England and Wales, Company number 8314911
VAT Registered in the UK, number 182 0661 19
Registered Office: Amelia House, Crescent Road, Worthing, BN11 1QR
On 01/02/2019 00:33, Adam Armstrong via observium wrote:
Hmm...

Originally the plan was to try to implement alert coalescing so that multiple alerts would be sent in a single email, but that isn't as easy when you don't only use email.

I could potentially add *device* dependencies, which might be easier to implement and handle.

adam.

On 2019-02-01 00:23:22, Joey Stanford via observium <observium@observium.org> wrote:



In reality we don't actually know if anything is up or down, we only know that something /was/ up or down at some point in the past.


At least in our situation, there might a programatic solution that could work. 

1) set a delay to the alert (we have this already as part of the checker)

2) set a variable for the number of pending (concurrent) alerts.  e.g. 10

3) If number of pending alerts > threshold send alert storm alert and purge alert queue

Something along those lines would probably work to cut down the spam at least in our case.

ps one of my guys said "We need to get Joey to program Obs so that when we get this many alerts it plays a tune😁”  I told them that tune would like be an air raid siren.


_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium