Page History

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

opEvents 2.0.4

This version of opEvents was released on 12 Feb 2016. It introduces numerous new capabilities and fixes for various bugs and minor problems.
The  major changes are new and improved timezone handling, more flexibility for event storm control and correlation and better event action policy processing.

• opEvents' timezone handling was greatly extended.
  If you set the config option omkd_display_timezone to your desired timezone, then all times in the opEvents GUI will be displayed in that timezone and including the timezone offset.
  You can use any timezone definition from the ISO8601 standard and the Olson database, plus "local" (meaning the timezone configured on the server).
  If this option is not set, the times will be shown in the "local" timezone but without zone offset. If explicitely set to "local", the offset suffix is shown.
• opEvents now supports times with timezone specifications in the advanced search dialog (but  only in numeric offset format at this time, e.g. "+0500").
• opEvents now records the original event date property (if any) separately from the underlying raw epoch time, and timed records for all of an event's processing stages are recorded as well.
  All of these are shown on the event details page.
• Escalation policy actions are now shown more prominently in the action log display.
• The handling of special characters in policy action substitutions was improved, and the example EventActions policy file updated.
  Please note that the EventActions file shipped with version 2.0.3 is insufficiently robust and should be replaced with the new version at your earliest convenience.
• The log handling was improved. Log reopening works more reliably, and opEvents daemon logs are now prefixed with the component role and process id.
• Improved robustness for the rest-style API for remote event management and the example client application.
• New mechanism for displaying a dynamic service priority text (by event tagging with servicePriority).
• Improved robustness and efficiency for MongoDB operations.
• opnode_admin is now able to clean up inconsistent semi-existent nodes, including events for that node.
• opEvents can now optionally ignore events for unknown nodes.
  This is configured using the configuration setting opevents_auto_create_nodes, which defaults to true if not present. If true, node records are automatically created if necessary.
  If set to false, no nodes are automatically created and events for unknown nodes are completely ignored.
• The GUI authentication expiry can now be adjusted with the configuration setting auth_expiry_seconds.
• Various opEvents GUI pages were adjusted for improved usability and better access to events' context and details.
  For example, the event context for stateful events now includes links to any related/opposite event.
• opEvents now performs policy actions email and script asynchronously and in separate processes.
  This speeds up event handling substantially because the main event reader process does no longer have to wait until the programs that your action policy triggers actually do finish.
  (For example, diagnostic programs like traceroute can easily take 30 seconds to complete.)
  If an event has actions pending processing or completion, a notice info bar is shown on the event context page.
  The new config option opeventsd_max_processes lets you set a limit for parallel worker processes; if that limit is exceeded, further action processing is queued and performed later.
• Storm control and event correlation capabilities were improved.
  Both programmable event suppression and event correlation polices now support the option to automatically acknowledge the suppressed/triggering events. Furthermore they also allow the optional delaying of event policy actions for a configurable extra delayedaction period.
• opEvents now supports high-precision timestamps better, and displays both human-friendly and raw time stamps on the event details page.
• Stateless events sourced from NMIS' event log (or slave log) are handled more consistently and robustly, and only events with both state and stateful properties are interpreted as stateful.

opEvents 2.0.3

This maintenance release was released on 7 Dec 2015.

...