It's not really a plugin as it is only stored in mysql database. Good point is it recquires no code modification neither in zenoss nor in GLPI.
Here is what is implemented at the moment: - A new event in Zenoss create a new ticket in GLPI - Moving an event in zenos history, change the ticket status to waiting and to low priority (thus making oyu able to follow easily auto solved problem ) - Closing a ticket in GLPI move the event to zenoss history - If an event A has happened (and thus opened a ticket). an event B with the same dedupid (except for the priority part) won't open a new ticket, but change the ticket priority - If an event with the class /Status/Ping had happened on a device, following events on the device won't open ticket. As soon as the ping event is back to the history, new occuring event will open ticket again - All event in the class /Monitoring won't open ticket before their 3rd occurence. This allows to suppress SSH commands events in case of down host (it'll be detected by the status ping) or a short network problem. - Avaibility to adjust a ticket criticity: for the moment criticity in GLPI = criticity in zenoss + Prodstate of the device where prodstatse goes from 0 to -4 I'm open to any other suggestion ;) ------------------------ Nicolas Morey-Chaisemartin -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=9044#9044 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
