Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: release notes for 2.4.0

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

opEvents 2.4.0

This major release of opEvents was released on 27 Jun 2017.

Please note that the licensing system has been updated, and existing licenses will not work for opEvents 2.4.0: You will have to obtain an updated license for this version of opEvents.
You can check your licenses by visiting the My Licenses page; If unsure about your options, please email contact@opmantek.com.

GUI and CLI

  • opEvents has been completely reskinned and all pages have been reworked for easier navigation and greater consistency, e.g.  to offer similar types of quick-search and display options.
    This change also offers certain new options for customising pages.
  • The welcome page at /omk/ now shows which of your installed applications have newer versions available.
  • It is now possible to acknowledge events in bulk from the Current Events page.
  • Editing nodes from the GUI is now more context-sensitive; when done you're transported to the page that you came from.
  • GUI pages that support regular expressions for searching now offer both case-sensitive and case-insensitive regular expressions;
    Please note that case-insensitive regular expression searches are substantially slower and resource-intensive.
  • The opEvents CLI now allows searching for stateful elements by time of last state change.
  • The event status history and event actions taken are now more consistent and easier to see on an event's details page.
  • The event context page now shows the  linking between related events in greater detail, e.g. stateful opposite events as well as synthetic and suppressed correlated events.
  • opEvents now supports Delegated Authentication.
  • The Help menu now provides access to MongoDB status information.
  • opEvents' CLI tool was streamlined for faster operation if it is used as an event forwarder with act=create_event.

 Processing Backend

  • The opEvents processing pipeline has been updated to perform more actions in parallel for improved performance.
    All input parsing and event (action) processing is now handled in separate independent processes, and all log entries are suitably prefixed to identify the active party.
    New config options opeventsd_queue_cycle and opeventsd_file_cycle control how often these processes check for pending work.
  • Inbound log processing was made more robust wrt. file rotatation and  now also handles logfiles that are growing faster than opEvents can consume data; suitable warning log messages are created if such a situation is detected.
  • All automatic opEvents daemon restarting  is now subject to exponential backoff to limit the system load. In this version it is also possible to configure the opEvents daemon to not restart when configuration files are changed; see config option opeventsd_restart_on_config_change in opCommon.nmis for details.
  • opEvents can now optionally keep consumed JSON event inputs in an archive directory, instead of deleting them after consumption.
    See the config option opevents_move_json_logs in opCommon.nmis for details.
    The processing order of JSON event inputs was also adjusted to simplify debugging.
  • Event actions of type script whose handler programs crash are now retried a limited number of times only, and opevents_max_action_queue_age is checked  for such retries.
  • Flap detection is now more consistent wrt. the delayed action time window, and a suitable warning is logged if an event is too old for the flap detection logic to perform reliably.
  • opEvents now offers configurable Flap Event naming; see config option opevents_flap_name in opCommon.nmis for details.
  • It is now possible (but not recommended) to disable all DNS use in opEvents.
  • If desired, opEvents can be configured to not product Raw Log entries for blacklisted inputs. The default choice is to raw-log such inputs, but see config option raw_log_black_list in opCommon.nmis for other options. Raw Log data in general was made more consistent and complete, regardless of type of event input.

Other Changes

  • The opEvents installer now supports better control in non-interactive mode.
  • The parsing of event action policies was made more robust so that verbatim text like X.Y is not inadvertently expanded and lost.
    It's recommended nevertheless that you escape such problematic tokens with a backslash, e.g. X\.Y.
  • numerous smaller improvements and bug fixes.

opEvents 2.2.1

This maintenance release was published on 30 Jan 2017.

...