How do I re-arm an event or re-traverse the notification path for an already notified event
JohnD Blackburn <[email protected]> Thu, 30 Aug 2018 06:24:35 +0000
| Newsgroups | gmane.network.opennms.general |
|---|---|
| Message-ID | <AM6PR0602MB3381E80728785EB091A99A3FCB080@AM6PR0602MB3381.eurprd06.prod.outlook.com> |
How do I re-arm an event? That is, currently I have a custom notification path defined that creates a ticket in our ticketing system (Remedy Force). The problem is that if, for example, someone closes a ticket raised for a service being down, without actually taking action to bring the service back up, the service remains down, and no further notification is raised. What I need is a method to re-arm an event when the ticket is closed to force OpenNMS to re-raise the Notification. Alternatively, a way of telling opennms to traverse a notification path at regular intervals while the condition that caused the event exists. (my ticket submission code already prevents duplicate tickets being created, so regular notification path traversal would not generate duplicate tickets, but would create a new ticket if the 1st ticket got closed by a lazy user...) OpenNMS version: 22.0.3 Regards John Blackburn ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-discuss mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-discuss