When OpenNMS is restarted, ticketing plugins lose state. Please allow ticketing to be pushed to a message queue - Kafka, JMS, etc - so plugins can consume their work from that queue. This will allow ticketing to resume where it left off after OpenNMS restarted.
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Chandra Gorantla May 19, 2022 at 6:27 PM
May not be able to depend on external systems like Kafka/ActiveMQ. Can dump the state to Postgres as Json and retrieve while restarting.
Will Keaney May 19, 2022 at 5:42 PM
@jeffg I believe that is a reasonable conclusion.
Jeff Gehlbach March 8, 2022 at 4:08 PM
if I'm understanding this issue correctly, there would also be work needed in each the ticketer plugin to enable it to take retrieve the ticketing state from the broker and pick up where they left off. Do I have that right?
When OpenNMS is restarted, ticketing plugins lose state.
Please allow ticketing to be pushed to a message queue - Kafka, JMS, etc - so plugins can consume their work from that queue. This will allow ticketing to resume where it left off after OpenNMS restarted.