Thank you for providing the TrapDirector Module. It does seem interesting and I’m going to try it out.
We have hundreds on telco devices which send lots of traps every days and we currently have Zenoss to handle them. I wonder if this module and icingaweb2 can handle hundreds of devices and lots of traps coming from them?
We also have transforms and event mappings for the traps. Does this module support that ?
Without optimization, the system can handle 5-10 traps per second on a standard virtual server so I would say yes for trap handling of hundreds of telco devices.
About transforms & mapping I will need details about it before answering, but here is how it works for trapdirector :
You setup a list of trap handlers defined by host (or hostgroup) and trap OID.
Each handler has a rule which uses logic operators between trap data values to decide to trigger a ok/warn/crit to the service defined in handlers.
See this part of the doc : Rule eval
(Note : it’s not in the doc for now but you can use regexp on trap data OIDs, see : issue#16)
Complex transform can also be handled using hooks (not in the doc and no public released for now).