Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

New TicketerServiceLayer that uses Drools in order to allow users to create custom Tickets from Alarms

Description

The DroolsTicketerServiceLayer expands the functionality of the DefaultTicketerServiceLayer allowing users to create their own Tickets from Alarms using complex business logic.

This is useful in cases where ticket fields are dependant on factors such as alarm type, node name, node assets, foreign source, etc...

Patches are attached.

Acceptance / Success Criteria

None

Attachments

3
  • 31 Oct 2012, 11:47 AM
  • 31 Oct 2012, 11:47 AM
  • 31 Oct 2012, 11:47 AM

Lucidchart Diagrams

Activity

Show:

Benjamin Reed April 10, 2013 at 5:50 PM

Whups, forgot to close this.

Benjamin Reed December 10, 2012 at 3:08 PM

Thanks, refactoring looks good. I've merged it into master. Only 1 small change, you had a hardcoded /opt/opennms in your drools-ticketer.properties file.

Jesse White October 31, 2012 at 11:49 AM

I've attached the updated patches.

The feature has been moved to a separate sub-project in features/ticketing and I've added some test cases.

Jesse White October 31, 2012 at 11:47 AM

Updated patches.

Jesse White October 5, 2012 at 9:26 AM

Thanks for the feedback. The first two patches are independent of Drools and add the required plumbing, can you we look at merging these for now?

I'll try moving the implementation to a sub-project.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created May 19, 2012 at 12:59 PM
Updated January 27, 2017 at 4:21 PM
Resolved April 10, 2013 at 5:50 PM