opEvents 3 Release Notes are at the bottom of this page

Table of Contents

...

Download opEvents here - https://opmantek.com/network-management-download/opevents-download/

opEvents 4.

...

3.

...

9

Support for MongoDB 4.2 please see Upgrading to MongoDB 4.2

CAVEAT: EventNmisRules.json was updated to include parsing for various NMIS events, including for Enterprise Services, this was missed from the final build, the included file should be used to replace /usr/local/omk/install/EventNmisRules.json and /usr/local/omk/conf/EventNmisRules.json if you would like the new events handled automatically.

opEvents 4.2.1

...

 14 Mar 2024

Improvements

• Added support for Outages custom node properties.
  Please see opCharts - Scheduled outages for more information.

opEvents 4.3.8

Improvements

• Added support for Debian 11 to the installer

opEvents 4.3.7

Bug Fixes

• Modify the screen names and hyperlink names in opEvents Views to match their Views menu name.
• Fix spacing issue for Busiest period incidents column in opEvents Daily/Weekly Summary Reports.
• Fix event params in advanced GUI filter for opEvents Dashboard.
• Fix the 'Event List' hyperlink to point to correct address in Current Events.
• Updated opEvents API documentation to use "o_node_name" parameter in place of “o_node”.

opEvents 4.3.6

Bug Fixes

• Fixed the bug that was causing Realtime connection to fail in Redis.

opEvents 4.3.5

Improvements

• The Events and Current Events pages now support searching for priority expressions, in realtime mode, for example >3, <=6, !5, 5-7
• opEvents node details will now display REDACTED data for node configuration data like authpassword

Bug Fixes

• Fixed the bug that was causing SNMP to fail in Administration Node tools.
• Bulk upload of nodes in Administration is no longer activated for opEvents by default, the uploaded data is now used.

opEvents 4.3.4

Bug Fixes

• Fixed a bug in the file install/EventNmisRules.json that was leading to an error being reported by the installer while checking for configuration changes. The error in the file has now been fixed.

opEvents 4.3.3

Improvements

• opEvents now supports adding Notes to events. 
  • You can add and edit the Note Title on the Events and Current Events pages.
  • You can add and edit the longer Note Text and the Note Title on the Event Context screen.
  • You can specify the search criteria as Note Title and search for specific Title on the Events and Current Events pages.
• Enterprise Services Event Correlation, nodes associated to an enterprise service are tagged with event properties, so overall visible events are reduced.
• Added support to edit and delete Saved filters on the Current Events page.
• The Events and Current Events pages now support searching for priority expressions, for example >3, <=6, !5, 5-7
• Added support for Planned Outage Open and Closed events in EventNmisRules.json

Bug Fixes

• Fixed the bug that was causing the API calls with the event.time argument to fail.
• Fixed multiple bugs in the opEvents filters related to -
  • Saving Filter Names with blank spaces
  • Search being truncated due to ? symbol in the filters
• Fixed the bug that was causing the Export to CSV function on the Events page to misbehave.
• Fixed the bug that was causing the opEvents GUI refresh function to fail to synchronize with the system time.
• Fixed the bug that was causing the opEvents toolbar to not display the Node Context name and URL.

Caveat

The file install/EventNmisRules.json was updated to include rules for Planned Outage Open and Closed events, unfortunately there was an additional comma after the last rule which causes the installer to show an error message while checking for configuration changes. This has been fixed in opEvents 4.3.4. Update to the latest version of opEvents, then follow the instructions to update your EventNmisRules.json file with the changes.

opEvents 4.3.2

Improvements

• Add Save Filters for Current Events so that you can save your filters and reuse them later.
• Add a link from opEvents event context to the affected Enterprise Service.

• Add an option to allow insecure certificates (expired, self-signed, etc) when creating remote events. Config item omk_ua_insecure. 0 (off) by default, change to 1 to enable insecure certificates.

Bug Fixes

• Fix bug with filter working on the event name, but NOT applying the filter to new events coming in, so now in real-time mode, only events matching the filter are displayed. 
• Fix subsequent synthetic events being raised as expected.
• Fix the Pie chart and Time Series chart on the main dashboard so that the both show the top 10 nodes.

opEvents 4.3.1

Improvements

• This release includes improvements in graph colors and various UI bug fixes.

Bug Fixes

• Fixed the nodes and colours mismatch between graph and pie charts.

opEvents 4.3.0

Big release with an upgraded GUI framework to deliver accessibility enhancements and dark mode.

Improvements

• This release includes improved Accessibility options, including support for Dark Mode. We have taken the opportunity while we tidied up the screens to change Opmantek to FirstWave. These are new features that are backward compatible with earlier releases.

• Improved event actions index, when you have a high number of action logs in MongoDB there would be a slowdown in fetching these records.

Bug Fixes

• Fixed issue where a call to custom node context links shown in a data-grid cell on Events index page would cause excessive warning logs to opData.log
• Fixed issue where attributing a node to a newly ingested events host would not lookup other interfaces attributed to the node. We have also added configuration.host_backup to this lookup.

opEvents 4.2.2

Improvements

• Support for MongoDB 4.2 please see Upgrading to MongoDB 4.2

Caveat

EventNmisRules.json was updated to include parsing for various NMIS events, including for Enterprise Services, this was missed from the final build, the included file should be used to replace /usr/local/omk/install/EventNmisRules.json and /usr/local/omk/conf/EventNmisRules.json if you would like the new events handled automatically.

opEvents 4.2.1

Internal release only

opEvents 4.1.1

GUI Changes

• You can now click on the event to select it for bulk acknowledging
• A clear filter form button has been added to the filter modal.
• Multi parameter search has been added, you can make computer AND queries.
• Filtered websockets, if you are using realtime and you have filtered the grid for example node name "abc" events with the node name "abc" "abc123" etc will be show, all other events will be not be delivered to the gui. Clearing the filter will clear filtered web socket.
• Comments now use a human readable timestamp
• Fixed issue with the acknowledged button not displaying correctly.
• if you configured the grid to show more than 500 events realtime event will be paused.
• If opEvents parses a Enterprise Service event the gui will show a button to link back to the related enterprise service on the same server. Note this will not work in a multi server operation.

Engine Changes

• Fixed issue where copy_first or copy_last in event correlation would not be able to copy the node name, this caused the synthetic event to use the global node name. if you have been using copy node in the correlation rule you should replace this with node_uuid
• Script outputs in emails will now render correctly
• New plugin interface to easily work on other events in parser plugins, docs coming.
  • In a parser plugin the third argument is now a helper interface replacing the full opEvents object.
  • Setting opevents_parser_plugin_use_events_obj to true will allow you to use the full opEvents object to retain pre 4.1.1 functionality

• opEvents will check if the events node is currently in an outage which is set in NMIS9 or opCharts.

  • "opevents_associate_outage_term" in opCommon.json will be used as the event property for an outage

  • The default property added is "planned_outage"

  • This value will be set to "true" / "false" if the outage is current.

  • setting opevents_associate_outage_term to null or removing the key from opCommon.json will turn the feature off

Internal release only

opEvents 4.1.1

...

GUI Changes

• You can now click on the event to select it for bulk acknowledging
• A clear filter form button has been added to the filter modal.
• Multi parameter search has been added, you can make computer AND queries.
• Filtered websockets, if you are using realtime and you have filtred the grid for example node name "abc" events with the node name "abc" "abc123" etc will be show, all other events will be not be delivered to the gui. Clearing the filter will clear filtered web socket.
• Comments now use a human readable timestamp
• Fixed issue with the acknowledged button not displaying correctly.
• if you configured the grid to show more than 500 events realtime event will be paused.
• If opEvents parses a Enterprise Service event the gui will show a button to link back to the related enterprise service on the same server. Note this will not work in a multi server operation.

Engine Changes

• Fixed issue where copy_first or copy_last in event correlation would not be able to copy the node name, this caused the synthetic event to use the global node name. if you have been using copy node in the correlation rule you should replace this with node_uuid
• Script outputs in emails will now render correctly
• New plugin interface to easily work on other events in parser plugins, docs coming.
  • In a parser plugin the third argument is now a helper interface replacing the full opEvents object.
  • Setting opevents_parser_plugin_use_events_obj to true will allow you to use the full opEvents object to retain pre 4.1.1 functionality

Admin Changes

• Fixed issue where changing a password would break Users.nmis group authentication.

...

• Updated core dependencies
• Cookies now support samesite strict, see Security Configurations
• Fixed issue in checkdaemons.sh with stopping monogdb

opEvents 4.0.4

Improvements

• opevents_auto_create_nodes is now disabled by default and has to be explicitly set to "true" for nodes to be created.
  
• opevents_event_copy_node_properties allows node catchall to be copied to the event, this allows event rules for example to be created
  

  • event.nodeinfo.catchall_data_sysLocation =~ qr{Odin}

Bug Fixes

• Fixed issue where an event update without real-time enabled would try and push an update over Redis. If Redis was not configured timeout errors would appear in the logs.

opEvents 4.0.3

Improvements

• Event Context has been updated to support realtime updates over web-sockets.

  • Preforming event actions while in realtime mode will not refresh the page to get the new data

  • Nodes Details is rendered below the Event Context and allows full length rendering of host names which would cause overflowing before.

  • The event context panel is now rendered with a JavaScript template both in realtime and non realtime. If you prefer the old template style rendering or you have made chnages to the html template you will have to enable legacy panels

    • opevents_gui_event_context_legacy_panels : "true" , you cannot set this option if you want the GUI to work in realtime mode.
      

  • When an event is updated we match the changed keys to then produce the web socket event to update the GUI, some users may have custom keys in the event and may be calling updateEvent through plugins r
    • Using opevents_realtime_push_on_key you can add extra event keys to this array to make sure the GUI updates on changes.

• Multiple outputs of a script can be saved to a an event. When a script output has been saved we have moved from storing this as a top level key eg script_<scriptname> to having an array of scripts script[{},{}]

  • The hash is stored as keyvalue pairs inside an array

    • _id is the id of the queued event action which stated this script operation

    • time is the completion time of the script

    • script is the name of the script

    • cmdoutput is the output of the script

    • exitcode is the code produced when the script terminated

  • If you have been using a script output in the gui, for example opevents_gui_event_context_summary_list we have retained the old method of asking for the script output.

    • If there are multiple script outputs saved from the script being run multiple times the last script will be used for display in the GUI.

    • In opevents_gui_event_context_summary_list using script.ping_node will get the cmdoutput for this script

      • Calling script.traceroute.time will get time of this script

  • If you have been accessing scripts in Event Plugins you will have to modify your code to accept an array from script and loop through the array till you haved matched the script output name you are interested in.

• opevents_gui_current_events_priorities has had issues with keeping sorted when we changed to json configuration, we have introduced the config options
  

  • opevents_gui_current_events_priorities_lower & opevents_gui_current_events_priorities_upper which have superseded opevents_gui_current_events_priorities.

• Event context Recent event and actions taken grids page size can be configred with
  • opevents_gui_event_context_events_pagination
  • opevents_gui_event_context_actions_pagination

Bug Fixes

• Fixed issue where the notes set for a node would not display in the event context.

opEvents 4.0.2

Improvements

• You can now pause and start realtime events by using the controls in the top right of the screen.
• New config option to change the default sort of recent events, opevents_gui_recent_events_default_sort
• Removed the toast dialogs for realtime events and the grid now shows the websocket status and if it has connected to redis.
• improvements in the UX from switching between server mode and real time mode when searching or sorting realtime events
• Improved the collection handling in removing old events
• When the realtime connection to redis connects the collection will autofresh to make sure the GUI has the latest section of events before new events are added

Bug Fixes

• Fixed issue where the grid total could would not reflect what was in the collection
• Fixed issue where the realtime collection being put into server mode would not respond to the refresh button in the top right of the gui

opEvents 4.0.1

Improvements

Big release which publicly releases real-time events, please see opEvents Realtime Events page to learn more about this feature, current caveats and using web-sockets with HTTPS.

• New nmisx method to create events in NMIS
• opEvents plugins now allow use of the self object inside the plugin
• opevents_realtime_events_max_age new config option to only push events to the GUI which are younger than this value.
• The reconnect option enables auto-reconnection mode. If we cannot connect to the Redis server, or if a network write fails, we enter retry mode. We will try a new connection every every microseconds (1 ms by default), up-to redis_reconnect seconds.
  • New options in opCommon.json for this
    • redis_reconnect
      
    • redis_reconnect_every

Bug Fixes

• Fixed issue where realtime updates would not push any data under key nodeinfo.X
• Fixed issue where the installer could not preform migrations from opEvents to 3 on remote mongo instances.
• opEvents EventAction.json is throwing error when using event.priority on condition field.
• Fixed issue when looking at redis db info with the db not connected would cause a page crash

opEvents 3

opEvents 3.3.0 (Internal release)

...

Please see opEvents Realtime Events page to learn more about this feature, current caveats and using web-sockets with HTTPS.

Bug Fixes

• Fixed issue where Classic Auth group check was giving unexpected results.

...

Improvements

• New nmisx method to create events in NMIS
• It sends self object to the Events plugin

Bug Fixes

• Fixed issue where the installer could not preform migrations from opEvents to 3 on remote mongo instances.
• OpEvents EventAction.json is throwing error when using event.priority on condition field.

...

New action in opcharts-cli setup-db, this updates oPEvents indexes in MongoDB on install and can be manually run from the cli.

Bug Fixes

• Fixed issue in opEvents where a large amount MongoDB connections were created and retained.

...