The opennms default event configuration for handling events contain not just OpenNMS internal used events, they also contain IETF MIB specific event definitions. These definitions are spread between default.events.xml, Standard.events.xml and opennms.events.xml. The configuration file which have those events should be separated to be maintainable and easier to upgrade. Special events which catch-all should named clear and not just defaults.events.xml. The IETF events should be moved into separate event files to allow users to remove them easily from eventconf.xml when not needed.
Tabs are removed, they currently normalised with 4 space indentation, which was described here: https://wiki.opennms.org/wiki/Code_conventions. I personally don't care as long we do all the same
David Hustace February 12, 2017 at 3:32 PM
When you do this clean up, could you also standardize the XML formatting? *Get rid of tabs *Two space indentation
The opennms default event configuration for handling events contain not just OpenNMS internal used events, they also contain IETF MIB specific event definitions. These definitions are spread between default.events.xml, Standard.events.xml and opennms.events.xml. The configuration file which have those events should be separated to be maintainable and easier to upgrade. Special events which catch-all should named clear and not just defaults.events.xml. The IETF events should be moved into separate event files to allow users to remove them easily from eventconf.xml when not needed.