Page History

This is a brief overview of the major changes between opEvents releases.

opEvents 1.2.3

opEvents 1.2.3 was released on 24 Nov 2014.

• This version includes a helper for setting up MongoDB for Opmantek use, and the installer offers to run the helper on installations and upgrades.
• opEvents now supports per-node licensing and activation: nodes can be marked disabled from within the GUI, in which case the node does not count for license limits and no events are handled for this node. By default all nodes are active.
• The node configuration infrastructure in opEvents is now fully unified and shared with opConfig.
• Renaming nodes in opEvents now also renames all past events for that node.
• opEvents now includes a full-featured command line tool for node administration, bin/opnode_admin.pl . This tool implements all node management functions already present in the GUI, as well as some extras to make it suitable for scriptable node creating and editing.
• The ordering of rules in the event action and parsing engines was fixed (under certain circumstances rules could be tested in the wrong order in older versions).
• The default event action rules were improved to better collect diagnostic info in reaction to node- and network-related events.
• The event action tag.name(value) has been improved to not clash with internal properties.
• The event action email(recip) has been revised for better standards compliance and interoperability with IP version 6.
• opeventsd.pl now handles inadvertent log replays better. It can be told (with config option opevents_max_event_age) whether older event inputs should be processed or skipped. The handling of missing, malformatted or otherwise indigestible log files was made more robust.
• If no opEvents license is present, then oeventsd.pl starts but doesn't consume any incoming files; it also creates a log entry about  the missing license once every 15 minutes.
• opEvents now supports setting a custom PATH environment for running script/program event actions. If you set the config option opevents_standard_path, then opEvents will set that PATH for all external programs that it runs.
• Opmantek applications can now be selectively enabled using the configuration option load_applications.
• The installer for opEvents was updated to improve robustness and reliability, and opEvents now ships with the Opmantek Support Tool.
• The display of errors and exceptions in the GUI has been improved.
• various minor improvements and bug fixes in both the GUI as well as the back end.

opEvents 1.2.2

This is a maintenance release incorporating bug fixes and some new featurefeatures:

• opEvents now support notes for both nodes and events.
  Any notes for nodes that exist in NMIS are imported when you use Import or Refresh from NMIS (in the System->Edit Nodes menu).
  Notes for events can be edited by users with privilege Module_opEvents_rw or higher. Notes for nodes require Module_opEvents_admin.
  Both types of notes are shown on the event and node context pages and can be of arbitrary length.
• Editing of notes for events is recorded (as an action named note) with the even, and tthe user making the change is included in the action log.
• opEvents now creates the necessary database indices automatically on the fly, and it is no longer required to run "opeventsd.pl act=setup" for database initialization.
• All opEvents pages were improved with regard to scalability and rendering delays have dropped substantially.
• opEvents' Advanced Search now supports searching by node (also with regular expression).
• The display of the event-over-time chart on the dashboard page was improved to display the  'busiest' node at the bottom of the stacking order.
• Compatibility with Internet Explorer 11 was improved.
• Both htpassword hashing modes (DES/Crypt and Apache-custom-MD5) are now supported.
• some installer improvements and various minor bug fixes.

...