Product Compatibility

Refer to product compatibility to determine supported Operating Systems and Database Versions.

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

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

opEvents 2.7.0

Improvements

• Added secrets randomise and secure cookies. For more information see Security Configurations. 
• Updated jQuery dependencies.

opEvents 2.6.5

Bug Fixes

• Fixed issue with Radius Authentication.

opEvents 2.6.4

Bug Fixes

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

opEvents 2.6.3

Released 30th March 2021

This version provides new authentication configurations:

• Limit the number of sessions per user
• Lock users that have not logged in in a specified period of time

opEvents 2.6.2

Released 13th January 2021

Fixed bug with programmable action buttons where the status of the currently executed action would return the completed status of the job even if the action was still queued or being processed. This only affected the visual indicator of the running action and refresh of the page, the action would have still be executedThis is a brief overview of the major changes between opEvents releases.

opEvents 2.6.1

Released 22nd December 2020

...

opEvents 2.6.0

Upgrade Notes

This release of opEvents 2.6 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

...

This is a maintenance release.

This release requires updated licenses, please contact Opmantek Support to organise new licenses.

...

opEvents 2.4.4

published 11 April 2019

Bug Fixes

• Fixed an issue where events being enriched by node proprieties clashing with the event authority key 'location',
  
  • opevents_event_copy_node_properties is now in a sub document on the event using the key nodeinfo
  • These copied properties be accessed like: nodeinfo.location
• Fixed an issue where setting the time period using the filter would not function

...

• Event Context and Node Context views have improved Event Actions and Node Event panels that auto refresh.
• Event Actions editor saves a draft on your browser’s local storage when you navigate away without saving. On return you can load the draft copy or discard it.
  • EventActions.nmis  is not affected until you Save.
• Table Schema Updates
  • Acknowledged By now shows if the event was system acknowledged in the table
  • Events group added
  • Location group added
• Events now have an editable event status.
  • This allows opEvents to be used as a technical service desk
  • Enable the feature in opevents_event_status_enabled  => 'true' in opCommon.nmis
  • Default status value on event creation can be set by opevents_event_status_default_value opCommon.nmis
    • Default Undef
  • Values which the operator can select are defined in opevents_event_status_values in opCommon.nmis
  • This is an array of hashes with the key being 'status'
  • If enabled or the event has the status property, a select box will be rendered in the event context panel
  • Event Action is generated when the event status is changed
• Events on creation can be enriched by node data. any value on the node can be utilised
  • Which properties to copy are defined in opevents_event_copy_node_properties opCommon.nmis
  • Array of node keys
  • Default is group and location
• Table schema now supports the property extra_css to define css classes for grid cells
• Event Context, Context panel can now display any key value from the event
  • Use opevents_gui_event_context_summary_list in opCommon.nmis to define which keys from the event you wish to display

Bug Fixes

• Fixed GUI performance issues affecting installs with a large amount of events

...

• The generic extensible parser now supports user-defined plugins, and offers new directives for resolving arbitary inputs using the DNS (forward and backward)
• The correlation system now provides much more fine-grained control over the contents of a synthetic event, as well as optional post-match inhibit times.
• opEvents now supports stateful synthetic events.
• Event Emails now provide better formatting for event script actions and status history.
• Various GUI simplifications and improvements
  • opEvents now offers three different default periods for the GUI
    Config option opevents_gui_dashboard_default_period is for the main dashboard page, option opevents_gui_console_default_period governs the 'Recent Events' console, and all other pages are controlled by opevents_gui_default_period. The default for all three is 2 hours.
    Furthermore the default choices for the period dropdown was expanded with some longer periods.
  • The event.host property that confused people repeatedly is now only displayed on an event's details page.
  • The Node Administration page now shows what applications a node is enabled for, and the node name now links to the edit dialog.
  •  Some of the more interactive pages now support a quick search for the most common properties, and the display of any active sorting was improved.
  • It is now possible to omit the Recent Events list on the Current Events page: simply set the values of config  item opevents_gui_console_pagination to <number of current events to show> and -1 (default is 10 and 10, respectively).
    • This can be used to hide Recent Events in the active_events screen which is titled Current Events.
  • The Raw Logs  page now shows much more detailed information about the disposal of input data; blacklisted, deduplicated and other ignored and discarded inputs are now shown with a brief explanation of the reason, and actual events are linked for easier access.
• opEvents now ships with its own CLI tool, and using the opeventsd.pl or opeventsd.exe for operations like import, report creation etc. is now deprecated (and results in warning messages).
  The tool opevents-cli.pl also incorporates the functionality of create_remote_event (which is still shipped separately).
• Element states are now better controllable and adjustable.
  If any nodes managed by opEvents should suffer desynchronised element states or carry orphaned/old undesirable states, this is now simple to resolve.
  In the node context GUI each element state can not be toggled or deleted outright if you are an admin user. On the command line, the tool opevents-cli.pl can list, show, create, remove and set any element state as necessary.
• opEvents now provides a safer, faster and more flexible interface to external processes for script policy actions.
• opEvents now supports a "macro" capability for accessing certain configuration values from an action policy IF condition, action policy script arguments, external enrichment arguments, or email templates. See the "macro" section in opCommon.nmis, and the discussion of macro.somename on the linked documentation pages.
• The parser rules were all updated for greater robustness, and the default parser for trap logs is now the generic extensible traplog parser.
  The example generic extensible parser rules were updated to support RFC3389/ISO8601 high-precision timestamps.
• Installer improvements for greater security
• opEvents now maintains both event priority and NMIS-compatible 'level' properties for an event. All internal logic continues to use 'priority' exclusively.
• opEvents now handles 'priority update' events from NMIS more user-friendly
  In the past, stateful events from NMIS which didn't convey a new state were summarily deduplicated. In this version, stateful events that carry a different priority (but the same state) are consumed and the original event is updated with the new priority, level and details. In such cases the event's "status history" (visible on the details  page) holds a record for each such change.
• opEvents can now save newly imported nodes from NMIS in disabled or enabled state (see the config item opevents_import_nodes_activated)
• Sensitive data is no longer imported from NMIS at all (e.g. SNMP communities).
• Imports from NMIS can now be limited to the primary node information (i.e. not importing any of the node's interface IP addresses that NMIS may know).
  This is selected using the configuration item opevents_import_node_interfaces, which defaults to true.
• Imports from NMIS can now optionally include or ignore the node, interface, SNMP and WMI state information.
  To include state updates from NMIS, add setstate=true overwrite=true to the import arguments. State updates are no longer enabled by default, except for newly added nodes.
• The node editing  GUI now offers the extra tab "Details", which presents all currently set configuration attributes of that node for diagnostic purposes.
• And of course various bug fixes and smaller improvements

...

• The handling of action policy processing was improved for better flexibility and consistency.
  A new config option opevents_auto_acknowledge_up has been added, which controls automatic acknowledgement of stateful up events. It compliments the existing opevents_auto_acknowledge option which controls stateful down events.
• The import of node information from NMIS has been improved for better reliability.
• Clicking on points on the dashboard charts is now more robusts and brings up the events in the respective time without further filtering.
• The example rule sets for the generic extensible parser have been extended and now include SNMP trap log processing (log type "nmis_traplog_alternate").
• Some database robustness and speed improvements were made, and the built-in parsers were adjusted for greater flexibility.
• opEvents now support high-precision timestamps for event inputs, if given in RFC3389/ISO8601 format (e.g. "2016-03-21T06:01:02.345+10:00").

...

• opEvents' timezone handling was greatly extended.
  If you set the config option omkd_display_timezone to your desired timezone, then all times in the opEvents GUI will be displayed in that timezone and including the timezone offset.
  You can use any timezone definition from the ISO8601 standard and the Olson database, plus "local" (meaning the timezone configured on the server).
  If this option is not set, the times will be shown in the "local" timezone but without zone offset. If explicitely set to "local", the offset suffix is shown.
• opEvents now supports times with timezone specifications in the advanced search dialog (but  only in numeric offset format at this time, e.g. "+0500").
• opEvents now records the original event date property (if any) separately from the underlying raw epoch time, and timed records for all of an event's processing stages are recorded as well.
  All of these are shown on the event details page.
• Escalation policy actions are now shown more prominently in the action log display.
• The handling of special characters in policy action substitutions was improved, and the example EventActions policy file updated.
  Please note that the EventActions file shipped with version 2.0.3 is insufficiently robust and should be replaced with the new version at your earliest convenience.
• The log handling was improved. Log reopening works more reliably, and opEvents daemon logs are now prefixed with the component role and process id.
• Improved robustness for the rest-style API for remote event management and the example client application.
• New mechanism for displaying a dynamic service priority text (by event tagging with servicePriority).
• Improved robustness and efficiency for MongoDB operations.
• opnode_admin is now able to clean up inconsistent semi-existent nodes, including events for that node.
• opEvents can now optionally ignore events for unknown nodes.
  This is configured using the configuration setting opevents_auto_create_nodes, which defaults to true if not present. If true, node records are automatically created if necessary.
  If set to false, no nodes are automatically created and events for unknown nodes are completely ignored.
• The GUI authentication expiry can now be adjusted with the configuration setting auth_expiry_seconds.
• Various opEvents GUI pages were adjusted for improved usability and better access to events' context and details.
  For example, the event context for stateful events now includes links to any related/opposite event.
• opEvents now performs policy actions email and script asynchronously and in separate processes.
  This speeds up event handling substantially because the main event reader process does no longer have to wait until the programs that your action policy triggers actually do finish.
  (For example, diagnostic programs like traceroute can easily take 30 seconds to complete.)
  If an event has actions pending processing or completion, a notice info bar is shown on the event context page.
  The new config option opeventsd_max_processes lets you set a limit for parallel worker processes; if that limit is exceeded, further action processing is queued and performed later.
• Storm control and event correlation capabilities were improved.
  Both programmable event suppression and event correlation polices now support the option to automatically acknowledge the suppressed/triggering events. Furthermore they also allow the optional delaying of event policy actions for a configurable extra delayedaction period.
• opEvents now supports high-precision timestamps better, and displays both human-friendly and raw time stamps on the event details page.
• Stateless events sourced from NMIS' event log (or poller log) are handled more consistently and robustly, and only events with both state and stateful properties are interpreted as stateful.

...

• The End Time selector was moved from the menu bar into the Advanced Search Menu.
• The Event List page now automatically refreshes.
• Selecting a different time period no longer disables auto-refreshing, and the default period for the GUI can now be configured with the config setting opevents_gui_default_period.
  The event context period can be configured independently with opevents_gui_event_context_period.
• The Event Context page now shows the escalation status for the event in question.
• The dashboard pages now show the events sorted by time, newest first.
• The logic for automatically acknowledging events was improved.
  A stateful up event now auto-acknowledges the corresponding down event and itself; in the past only the down event was acknowledged. This feature can be disabled by changing the config setting opevents_auto_acknowledge.
• A new action called acknowledge() is available for your Event Action Policy.
• Some code inefficiencies were removed, the event colors for priorities 9 and 10 were reworked for better contrast.
• This version of opEvents will work with MongoDB 2.4 but with reduced robustness,
  and only if you set the new configuration variable db_use_v26_features to 0.
  The installer now checks your local MongoDB's version and warns about this issue.

...