It is possible that an alarm gets cleared/resolved between the time a "createTicket" event was triggered, and the time that the actual ticket gets created. This can lead to scenarios where tickets are created for cleared alarms.
We should provide an option (that works irrespective or the ticketer plugin used) that allows us to avoid creating tickets in these cases.
Once this makes it's way into develop I'll flip the default value to true.
David Hustace November 15, 2016 at 12:35 PM
I would definitely make the default = true.
Benjamin Reed November 15, 2016 at 11:48 AM
The patch looks pretty straightforward to me. Question for after the merge, does it make sense to make the default true in 19? (I suppose doing so would require a documentation "breaking change" addition...)
Both of these cases can now be addressed by setting the 'opennms.ticketer.skipCreateWhenCleared' and/or 'opennms.ticketer.skipCloseWhenNotCleared' system properties. These default to false.
It is possible that an alarm gets cleared/resolved between the time a "createTicket" event was triggered, and the time that the actual ticket gets created. This can lead to scenarios where tickets are created for cleared alarms.
We should provide an option (that works irrespective or the ticketer plugin used) that allows us to avoid creating tickets in these cases.