Page Comparison

...

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.

...

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}

...

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

...

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

...

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.

...

Improvements

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

...