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

opEvents 2.0.0

This new major version was released on 13 Oct 2015.

• opEvents 2.0.0 requires NMIS 8.5.10G or newer for full interoperability. Please check the Product Compatibility page for details.
• Improved license management user interface
  It's now much easier to delete, restore or selectively import your licenses from your Opmantek.com account into opEvents,
  and reminders about any license conditions being exceeded are presented in a more useful fashion.
• There is a totally new rest-style API for remote event management, complete with an example client and its source.
• Configurable purging of old data from the opEvents database is now supported.
• opEvents provides a new facility for summary reports (created both on demand and periodically), complete with automatic email of reports as XLSX spreadsheet and online display.
• Comments with attribution and timestamps can now be added to nodes and events.
  Anybody who can view an event can also add a comment for it, but only an administrator can delete comments. (Node comments are all admin-only.)
  Comments are shown with the event or node in question, and are tagged with the creation time and originating user. Any URLs in comments are presented as clickable links.
  The older facility for importing and editing notes for nodes still remains.
• More user-friendly new landing and overview page at "http://<yourserver>/omk".
• Improved interactivity due to better database connection caching
  opEvents now keeps its connections to MongoDB open and reuses them as much as possible, which improves interactivity especially if you use a remote MongoDB server.
• New Node Overview screen
  There is a new node-centric dashboard or overview screen which shows events and event types for a node over time. Links between this node overview and the node context allow easy navigation.
• Various GUI improvements and  refinements, e.g. more informational window/tab titles.
• Improved NMIS importing now also covers opHA-slave nodes, and access to interfaces' ifAlias property
  Importing or refreshing  nodes from NMIS now handles nodes on remote slave instances if opHA is active on the opEvents server. Event action rules can now access an interface's Description or ifAlias property.
• Events can now include links to other "authoritative sources", e.g. external applications like helpdesk systems or the like.
  (See the documentation about authority and location properties in the list of Normalised Event Properties for details.)
• Node editing actions are now logged with timestamp and originating user in logs/audit.log
• Improved access control, better NMIS authentication integration
  opEvents now fully enforces access control based on a user's group memberships: only those nodes and events are visible, where the nodes are members of groups that this user is authorized to see.
  The installer now also offers to merge NMIS and Opmantek users.dat password files.
• Better logging and log-rotation support
  opEvents now logs to lots/opEvents.log and the log format was revised to make the logged information more useful. Logs are reopened when the opeventsd receives a SIGHUP signal.
• opEventsd now restarts automatically when any relevant configuration files change.
  opEventsd now can be instructed to also restart periodically, using the new opeventsd_max_cycles configuration directive (= restart after so many opeventsd_update_rate intervals).

opEvents 1.2.6

This version was released on 9 Sep 2015.

• This version interoperates fully with NMIS 8.5.10G, and requires at least this version of NMIS to be installed. Please check the Product Compatibility page for details.
• opEvents now works with MongoDB 2.4, 2.6 and 3.0.
• The Help/About screen shows more useful information, including a note about new releases. The window titles and icons have been updated.
• If installed together with opConfig or opAddress, then opEvents now provides links to node-related dashboards in those products  when possible.

opEvents 1.2.4

opEvents 1.2.4 was released on 2 Mar 2015.

• This is primarily a maintenance release, which does not introduce any new features.
• The installer was improved for greater robustness and ease of use.
• opEvents now supports sending Syslog messages to Syslog server over TCP and to arbitrary ports.
• a variety of smaller bugs were fixed as well.

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.
• a small warning: the installer may warn about two "incorrect checksum detected" for two files, if you install this version on top of the Opmantek Virtual Appliance version 8.5.6G or after other Opmantek applications that were released since opEvents 1.2.3. These warnings are benign and you can safely confirm that the installer is allowed to 'overwrite' those files.

opEvents 1.2.2

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

• 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.

opEvents 1.2.1

This is a maintenance release which primarily incorporates bug fixes.

• The help texts and tooltips in the GUI have been improved
• Role-based Access Control was added to the opEvents GUI.
• various installer improvements

opEvents 1.2.0

This is a general  release with various improvements and bug  fixes.

• opEvents now ships with the new Opmantek Installer, which provides a much simpler and safer installation and upgrade process.
• Restyled GUI, added glyphs for better visibility
• A GUI for Node management was added under the System menu, which also provides access to NMIS Node Import functions.
• New helper scripts for external event queue management were added
• Authentication logs are now separate in log/auth.log and no longer mixed into opdaemon.log.
• Entering a license is now simpler and requires just one click.
• The logic and heuristic for finding associations between IP addresses, short and qualified DNS names and node names was reworked and is now much more robust.
• Node names with "." in them work consistently now.
• The Modules menu was reworked and is more useful now.
• Improved opdiffconfigs, opupdateconfig and patch_config scripts are now shipped with the release.
• The daemon init scripts now work consistently on both Debian- and Redhat-style distributions, and provice a "status" command.
• The robustness of Quick and Advanced Search functions was improved.
• The presentation of the Element Up/Down was repaired and improved.
• The interoperability between Opmantek products has been greatly improved, and all products can now be installed in a cooperative fashion on the same machine.
• The GUI now displays a prominent warning on the main dashboard page, should there be no active opevents daemon.

opEvents 1.1.2

This is a maintenance release incorporating primarily bug fixes. The two noteworthy changes:

• A  security issue with the bundled Apache installation has been corrected, which could have been abused for denial-of-service attacks if opEvents was installed with unrestricted inbound access from the Internet.
• The licensing system has been updated: to evaluate opEvents you will require a new evaluation license. Full licenses are not affected by this change.

opEvents 1.1.1

• synthetic events are now subject to full deduplication and storm control
• the package now ships with suitable default log rotation config files
• improved robustness for log parsers and GUI behaviour
• reworked the interface between NMIS and opevents, opeventsd now offers more precise functions for initial import and subsequent refresh operatinons of NMIS node information.
  the GUI now also provides access to these functions.
• improved handling of stateful events for completely unknown nodes or devices
• email contents are now completely configurable in the form of any number of user-defined templates, which includes both email subject and body.
• the GUI now provides a link to the online product documentation.
• opevents can now log events as JSON files, implemented as a policy action.
• opevents now supports flexible watchdog timers for nodes and/or specific nodes' elements, implemented as policy action.

opEvents 1.1.0

• various GUI improvements
• opevents can now log events in NMIS syslog format, implemented as a policy action
• reworked stateful deduplication and event synthesis functionality for improved robustness

opEvents 1.0.6

• various bug fixes, node- and ip-cache-related, interaction between whitelist and rawlogging
• insertion of events from command-line or JSON files was reparied to fix a type issue that kept such events from showing up in the  GUI
• fixed an issue that could keep queued events pending for too long on a very lightly loaded system
• GUI updates to improve the display of events' context
• event emails were updated to contain more useful information
• supported policy actions now also include generic tagging of an event
• the escalation subsystem was made more resilient

opEvents 1.0.5

• overhaul of the mail sending infrastructure

opEvents 1.0.4

• fixes for external authentication methods and NMIS import issues

• opeventsd can now parse (and consume) NMIS logs in JSON format

Changes between releases 1.0.0 and 1.0.3:

• opeventsd now resurrects its worker slave on demand
• a new generic parser engine for local customisation was added
• opeventsd can now create events from the command-line or from a single JSON file
• opevents now supports any number of logfiles per log parser type
• the ip address cache now works properly and more efficiently
• opeventsd now displays all supported command-line arguments when run with -h or -?
• opevents now properly handles truncated (not rotated) logs