![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
See, this sort of thing is why we don't bother.
It's very complex, and unless you model a lot of different scenarios, it's only useful to a subset of users.
I actually don't think getting a bunch of emails during a failure is too much of a hardship. It encourages you to have fewer outages! 😆
Adam.
Sent from BlueMail
On 1 Feb 2019, 00:54, at 00:54, Joey Stanford via observium observium@observium.org wrote:
On Jan 31, 2019, at 17:33 , Adam Armstrong via observium
observium@observium.org wrote:
I could potentially add *device* dependencies, which might be easier
to implement and handle.
That might work but putting in dependencies for hundreds of systems will take a while. It’ll be a little tricky since we use OPFS to route around down devices. Keep in mind our system is about 50% RF links and then 50% devices. A device can have, in our topology, anywhere from one to 5 links to it. So a defined area would be fine…we could just make everything dependent upon the local router, but on larger sites it’ll be a bit more complex.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium