Page tree
Skip to end of metadata
Go to start of metadata

opEvents 4.0.3

RELEASED 6th September 2021

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

RELEASED 3rd August 2021

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

RELEASED 14th July 2021

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.3.0 (Internal release)

RELEASED 22nd April 2021

Large release which includes real time event updates over web-sockets, this includes a new 3rd party dependency to the product Redis which our installer will handle for you.

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.

opEvents 3.2.4

RELEASED 3rd June 2021

Improvements

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.


You can skip migrations by using the installer flag OPT_NO_MIGRATIONS=1

opEvents 3.2.3

RELEASED 19th March 2021

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.

opEvents 3.2.2

RELEASED 13th January 2021

New feature which shows programmable action buttons on events which operators to execute EventsActions scripts from the event context screen.

opEvents 3.2.1

RELEASED 13th November 2020

Upgrade Notes

Installer now handles the events migration when upgrading from NMIS8 compatible applications to NMIS9 compatible applications. To find out more about this upgrade please read: Upgrading Opmantek Applications

opEvents 3.2.0

RELEASED 30th September 2020

Upgrade Notes

The new upcoming release of opEvents 3 will work on Opmantek's latest and fastest platform, however, the currently installed products are incompatible with this upgrade. 
To find out more about this upgrade please read: Upgrading Opmantek Applications

opEvents 3.1.0

RELEASED 14th July 2020

  • Fixed bugs when searching for events, case intensive regex works now.
  • When searching for acknowledged events you can use 1 or 0, ack or acknowledged are substituted for a 1.
  • Use of json files tool for opEvents: The new OMK product version are using json files for configuration. This is a bit special for opEvents files, that uses more complex structures than other products: 
    • Regular expressions: The regex structure is not a valid object on a json file, that is why qr// is replaced by ''. They will be treated as regular expressions inside the code the same. The conversion tool will perform this replacement when the parameter replace_qr=t is sent. 
    • There is an exception with the EventActions file, where the regex is stringified, and will allow more complex structures. 
    • EventRules file also has another exception, as in the copy_* elements, there is the convention of the use of '//' when a regex is found. As the element is inside an array, and there is no possible way to indicate in the key that the element is going to be a regex. The conversion tool will perform this replacement when the parameter replace_copy=t is sent. 
    • Node structure: There is an internal change in the nodes structure due to the NMIS 8 to NMIS 9 compatibility change. At this stage the conversion tool does not cover this structure automatically and these changes should be done manually. 

opEvents 3.1.0B

BETA 8th Jun 2020

  • JSON Configuration files: The .nmis configuration files will be replaced by .json files
  • New License 2.0 structure used. 

opEvents 3.0.0

BETA

opEvents 3.0 is the NMIS 9 compatible version. 

  • No labels