Re: How do I re-arm an event or re-traverse the notification path for an already notified event

David Hustace <[email protected]> Mon, 3 Sep 2018 09:13:08 -0400

Newsgroups	gmane.network.opennms.general
Message-ID	<[email protected]>


> On Aug 30, 2018, at 18:17, JohnD Blackburn <[email protected]> wrote:
> 
> It would be great if OpenNMS had the ability to reset a service/node/threshold’s status so that the next time it checked, it is treated as if the previous status was ok/below threshold which would then trigger an event if it is still down/over threshold.. or be able to configure an event threshold/service status so that every time it checks, if it is down/over threshold still it triggers the notification.  A configurable notification mode so that it either notifies with the current method of notifying once and not again until the condition resets, or notifying after every check if the condition still exists.  This would enable ticket submission to automatically re-create the ticket if it has been closed before the condition was fixed, and is how a commercial monitoring product I have used in the past works.

Jira can be your friend.

https://issues.opennms.org


Cheers,
David


David Hustace
The OpenNMS Group, Inc.

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

signature.asc (application/pgp-signature, 873 B)