![](https://secure.gravatar.com/avatar/876f789f594a0616554e31d38678eb15.jpg?s=120&d=mm&r=g)
Haha we do not……I think I have another way with a wildcard match if the description is set. Is this something you guys are planning to do in the future? My co-workers are saying solarwinds does do that and it even checks to see if neighbours have dropped – likely via snmp-traps.
I know I can probably do this with observium’s syslog collector….i might just do it with splunk.
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: July 18, 2016 16:49 To: Observium Network Observation System observium@observium.org Cc: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Making an alert for mapped interfaces
Hi,
This information isn't available to the alerting associations system. (It's held in different tables, so would be complex to implement)
This is better done via port descriptions. All of your core ports have "Core" in their description, right? ;)
Adam.
Sent from BlueMailhttp://www.bluemail.me/r On 18 Jul 2016, at 21:25, Heston Kan <hestonk@oaky.netmailto:hestonk@oaky.net> wrote: Hey All,
I want to create an alert if any interface between two managed/discovered devices in Observium. This includes switchers and routers, servers…etc. I’d also like these to be based on Observium’s device Mapping that is available per device.
In the checker conditions I’d put hostname matches * but under the checker device and entity association. There’s no entity for mapped devices whether it be via CDP/LLDP or detected from observium itself.
Perhaps I’m missing the obvious.
Thanks! Heston
________________________________
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium