All, As seen by my last email, I'm building a module to service AdventNet's ServiceDesk product. I'm trying to understand the relationship between Events and TicketServiceLayer.
It seems the relationship is between Alarms and Tickets (ergo, Alarms create tickets). Is there any way to filter which alarms create tickets? It looks like all alarms create a ticket. Also, does alarms call Plugin.saveOrUpdate() using the existing ticket, until that alarm clears? After that, a new ticket is created? That would be beneficial, as I can add Notes to a ticket after it's been created for each occurrence of an alarm, until that alarm clears. Once an alarm clears, it sets it's internal ticket state to Closed? Thanks for helping me understand! -- Aaron J. Paxson --------- aaron.pax...@gmail.com http://aaron.thepaxson5.org ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
