Hi Erno, >>I also didn't like the "interface mask" stuff. The receivers should return >>the full interface name that the events consolidator will later use to >>create the alarms (if needed). > > > My example receiver _does_ return the full interface name: it uses the > interface mask to make it possible to use parameters to set up those > interfaces detected by snmp_table. I included snmp_table and the trap > receiver in one patch by no mistake 8) > > I do not deny that it's a bit specialized, although i tried to make it as > universal as long as it was fitting my purposes.
Ok, so the receiver should return an array with the mentioned fields and any extra fields the backend may use. > > >>So, in my point of view, you are 80% there. >> >>What do you think? > > > I'll wait for your reply about the backends, and then take a look in my code > to make the needed modifications. > You are right, having more than one backend doesn't hurt us, and make's us more flexible. So, there should be a backend called 'event' that inserts an event. You should have a traps_backends table too then. Javier -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Javier Szyszlican, Project Leader, JFFNMS [EMAIL PROTECTED] I hope JFFNMS or I were helpful to you, if you can, please donate at http://jffnms.org/donate ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ jffnms-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jffnms-users
