I'm trying to figure out a way to trigger notifications to get resent
based on some event.  My scenario is thusly:

We have a web gui which is extremely simplified for end clients.  We
integrated OpenNMS notifications to send messages to the web gui when
those few things happen that the client is interested in.  However, if
the web gui is down, it may not receive events, therefore when it
comes back up it's out of date.  So, when it comes up, I want it to
send a startup event to OpenNMS directly.  I use the automation shown
on the wiki 
http://www.opennms.org/index.php/Repeated_Notifications_Using_Automations
to find alarms and resend them through the system.  What I also want
to do is acknowledge the original event so that next time through the
automation I don't get re-triggered.

How to do this?  I tried adding a second <statement> which
acknowledges the startup event to the <action>., but the xsd doesn't
accept
multiple statements in an action.  So I have no way of both resending
the open alarms and acking the startup.

Any help?  Or is there a better way to do this type of thing?  I'm not
afraid of writing code (I've done it for a few other customizations
already) if someone gives me a clue...

--carl

------------------------------------------------------------------------------
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

Reply via email to