Define optional event parameters on the event definition

Description

There are several OpenNMS features that register event listeners and react upon the reception of an event.

When we're talking about hundreds or thousands of event definitions that require certain action, it is really hard and tedious to put all the hundreds or thousands of events on a XML configuration file like Scriptd's config.

If we have the ability to add custom parameters to events, we can define rules and/or actions based on these custom parameters when the event is received.

That way, the configuration files will be incredibly simple, and the filtering is done inside the listeners based on these optional parameters.

In order to support this feature in OpenNMS we need code changes on the event generation.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Alejandro Galue April 2, 2016 at 9:07 AM

Yes

Ronny Trommer April 1, 2016 at 9:18 PM

Seems to be fixed can we delete this branch? https://github.com/OpenNMS/opennms/tree/jira/HZN-551

Alejandro Galue December 2, 2015 at 5:39 PM

Here is an example about how to add a parameter to an event definition:

Alejandro Galue December 2, 2015 at 4:39 PM

The fix with updates for the XSD, the event definition classes, and the Event Expander with JUnit tests has been committed on revision 0c6e21ec2ee41e50e1ed0e264d760051a512edcc for branch jira/HNZ-551

Bamboo Track:
http://bamboo.internal.opennms.com:8085/browse/OPENNMS-ONMS314

Fixed

Details

Assignee

Reporter

Components

Affects versions

Priority

PagerDuty

Created December 2, 2015 at 3:24 PM
Updated June 3, 2019 at 7:53 AM
Resolved December 4, 2015 at 12:24 PM
Loading...