Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated release note to spell out mongodb version dependency

...

  • opEvents now offers free licenses which are not time limited (but limited to 20 nodes).
  • Please note that for performance reasons opEvents 2.0.2 requires MongoDB version 2.6 or newer.
  • opEvents now offers optional Single-Sign-On across servers.
  • The generic log parser now supports JunOS logs.
  • All irrevocable operations in the GUI now require confirmation.
  • Acknowledging events in the GUI is now recorded with username and timestamp, and this  information is shown on all relevant pages.
  • You can now enrich all or certain classes of events with links to external Knowledge Base systems.
  • Synthetic (aka correlated) events are now shown with links to the contributing nodes and events.
  • The Events Details page now shows all timestamps in both raw and human-friendly format.
  • Various GUI pages were reworked for improved performance, especially for (re)sorting by column.
  • The main dashboard and Event List pages now color events contextually, by event severity. If  desired, this can be disabled by changing the config  setting opconfig_gui_events_coloring.
  • For network interface events, opEvents now displays the elements with their interface descriptions appended in parenthesis (if the node was refreshed/imported from NMIS with opEvents version 2.0.2).
  • Syntax errors and other mistages in Event Action policies are now detected better and logged in log/opEvents.log, and log rotation in opEventsd was made more robust.
  • The Raw Logs functionality now records deduplicated and suppressed events with more useful details, i.e. the eventids property shows "deduplicated and discarded" instead of being blank.
  • opnode_admin now supports more user-friendly act=set and act=show operations, which let you quickly see and modify particular properties of a node; it can now also optionally delete nodes completely (=including their opEvents data). It also warns about (but still accepts) bad/less-compatible node names.
  • The opeventsd.pl actions for importing or refreshing nodes from NMIS were reworked for improved clarity and robustness, and the help text was rewritten.
  • The installer no longer overwrites user-customized CSS files (i.e. you can adjust public/omk/css/opEvents_c_custom_packed.css to your preferences and that will persist across versions).
  • ...and, as always, numerous smaller bugs and imperfections were repaired.

...