The sysContact will (should, but I don’t think anyone has relied on it pretty much ever) be used if no other contacts are specified for a given alert.

Our setup encourages people to set a default contact, because relying on sysContact got very messy very quickly. (imagine a stupid vendor who hardcodes it to their sales address, or who limits the field to 8 characters).

It might be easy/trivial/impossible for us to tie a “magic” email contact to be replaced with sysContact, though. I think this would solve your problem. I’d need to see if sysContact is indeed available at the necessary points in the code. (variable scope, how does it work?)

Adam.

From: observium <observium-bounces@observium.org> On Behalf Of Ryan, Spencer J. via observium
Sent: 22 April 2020 00:29
To: observium@observium.org
Cc: Ryan, Spencer J. <Ryan@millercanfield.com>
Subject: [Observium] sysContact-->Observium Contact

Is it possible to use a device’s sysContact (Either from SNMP or an override) to tie that to a specific observium contact, or is that for the email transport only?

My use case is that I want different devices to go to different pagerduty integrations, and the only way I can see to do that right now is to build different alert checks for each set, with the correct PD “Contact” associated with that checker.

Thanks in advance!

---

Spencer J. Ryan | Manager, Technology and Infrastructure

Miller Canfield

T +1.313.496.7979

---