[OpenNMS/opennms] 224a50: NMS-20101: Skip ticket creation when the alarm alr...
Marshall Massengill via opennms-cvs <[email protected]> Wed, 29 Jul 2026 11:03:11 -0700
| Newsgroups | gmane.network.opennms.cvs |
|---|---|
| Message-ID | <OpenNMS/opennms/push/refs/heads/mm/NMS-20101-smoke/[email protected]> |
Branch: refs/heads/mm/NMS-20101-smoke
Home: https://github.com/OpenNMS/opennms
Commit: 224a50e5ff78c9923bc721d19fa9f9eae48f2b7d
https://github.com/OpenNMS/opennms/commit/224a50e5ff78c9923bc721d19fa9f9eae48f2b7d
Author: Marshall Massengill <[email protected]>
Date: 2026-07-29 (Wed, 29 Jul 2026)
Changed paths:
M docs/modules/operation/pages/deep-dive/notifications/strategies/ticket.adoc
M features/notifications/ticket-strategy/src/main/java/org/opennms/netmgt/notifd/TicketNotificationStrategy.java
M features/notifications/ticket-strategy/src/test/java/org/opennms/netmgt/notifd/TicketNotificationStrategyTest.java
M opennms-base-assembly/src/main/filtered/etc/examples/destinationPaths.xml
Log Message:
-----------
NMS-20101: Skip ticket creation when the alarm already has a ticket
A group destination path target runs the createTicket command once per
member, and repeat notifications or escalations re-run it for the same
alarm; the ticketer creates a new ticket on every create event, so each
run produced another ticket.
Uses the tticketid the strategy already fetches to skip the create
event when the alarm has a ticket. Near-simultaneous deliveries can
still race the asynchronous ticket creation, so the examples and docs
now recommend a single-user target instead of a group.
To unsubscribe from these emails, change your notification settings at https://github.com/OpenNMS/opennms/settings/notifications
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/wiki/index.php?page=MailingListFaq
opennms-cvs mailing list
To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-cvs