Hi there. So the snmptrap daemon is working with Opsview fine, and we have services with rules defined which create alerts. All good.
But it seems that most traps which we choose to generate critical alerts on don't have an opposing "OK" trap which we can create a second rule to set the alert back to "OK". For example, say we have a switch which sends a trap about the fact it has a faulty power supply - and there is no opposing trap which is generated once the fault is fixed. In this case we will receive a critical alert and display a nice red marker in the Opsview GUI, but cannot make it go away - even once the problem is resolved. I wonder what strategies others use to deal with snmp traps in Opsview ? Thanks very much. _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/listinfo/opsview-users
