I wish it were that simple. We're using notifications to send a message over ActiveMQ message topic to an app server which is maintaining state for selective events for a customer-facing simplified GUI. If the app server goes down, it misses notification messages.
If a notification method fails (i.e. ActiveMQ is down) will the notification be queued up and retried? If so, I can just make the ActiveMQ channel a durable queue and my problem is largely solved. I've already written the ActiveMQ notification plugin for OpenNMS, so that part's done. Anyone know the answer to the failed notification/retry question? --carl On Wed, Apr 15, 2009 at 3:49 PM, Les Mikesell <lesmikes...@gmail.com> wrote: > Carl Nygard wrote: >> 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... > > I kind of like feeding notifications to an xmmp (jabber) group > conference (easy to set up with openfire). When you reconnect a client > it gives you a screen of earlier messages that you might have missed. > Email is even better at queuing missed notifications but having to > delete them is annoying and it is not as flexible as a jabber client in > terms of letting whoever wants to watch at any particular time get the > messages. > > -- > Les Mikesell > lesmikes...@gmail.com > > > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
