...

...

...

...

...

...

...

...

...

...

Product Compatibility

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

...

...

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

...

New feature to force an event status change when adding a comment. The feature needs to be on using the following configuration items: 

• 'opevents_event_status_enabled' => 'true'

• 'opevents_event_status_validation_on_comment' => [ 'non_empty_string', 'different_status' ],
  
  

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

opEvents 2.5.0

Released 15 July 2020

...

• New in-app editor for Event Actions and policies, this allows quick editing of you EventActions.nmis config, this can be found under "System" > "Edit Event Actions"
  • Syntax Highlighting for Event Actions
  • Validate your changes at any stage
  • Console output for event actions validation
  • Embedded documentation
  • Each save generates a new backup of your last revision these are saved in <omk_dir>/backups/EventActions.nmis.*
• Node context links are now viewable in opEvents. Docs for how they are used inside nodes at NMIS Linking Nodes to other systems. 
  • Node refresh from NMIS will be required to import these properties if changed on the node.
  • These show in the navigation bar for:
    • Node & Event Context
  • These show as links inside the data tables for:
    • Dashboard Screen
    • Events List & Current Events
• More robust handling of system overload situations
  • The main dashboard screen now warns if the event or action queues
    grow too large.
  • Any processing of events that have been stuck in the incoming queue beyond
    opevents_max_event_age (default: 2 hours) is now aborted and an appropriate
    entry is written to the raw log.
  • A new diagnostic API endpoint at omk/opEvents/health.json was added,
    which reports the opEvents daemon states and some metrics on queued overdue
    events and actions.
•  Resource safety limits for request periods
  • opEvents now by default sets the new configuration option
    opevents_max_period_value to 30 days, which ensures that no periods greater
    than that are selectable from the GUI. otherwise, selecting overlong request
    periods may cause memory exhaustion for both MongoDB daemon as well as the
    opmantek webserver workers.
• opEvents now installs a purging policy for old data by default
  (unless the admin answers 'no' when the installer prompts)
• The events dashboard pages now select a default display interval
  that extends slightly into the future (instead of cutting the interval
  off before the current time)
• The Opmantek web server now supports resource limits to alleviate out-of-memory situations
  • The two new configuration options omkd_max_requests and omkd_max_memory
    can be used to ensure that a web server worker process terminates after
    handling N requests (omkd_max_requests) or if it grows beyond M
    megabytes of resident memory (omkd_max_memory)
• New reorder protection feature for the handling of forwarded events
  this new feature (link to Deduplication and storm control in opEvents) was added to make the processing
  of forwarded events on a central server more robust
• Automatically refreshing pages are now more resilient in how they react
  to unreliable client clocks or browser timer events.
• Various bug fixes and robustness and efficiency improvements in both GUI and backend.
• Planned outages as reported by NMIS are now translated into stateful events by opEvents.

...

• opEvents has been completely reskinned and all pages have been reworked for easier navigation and greater consistency, e.g.  to offer similar types of quick-search and display options.
  This change also offers certain new options for customising pages.
• The welcome page at /omk/ now shows which of your installed applications have newer versions available.
• It is now possible to acknowledge events in bulk from the Current Events page.
• Editing nodes from the GUI is now more context-sensitive; when done you're transported to the page that you came from.
• GUI pages that support regular expressions for searching now offer both case-sensitive and case-insensitive regular expressions;
  Please note that case-insensitive regular expression searches are substantially slower and resource-intensive.
• The opEvents CLI now allows searching for stateful elements by time of last state change.
• The event status history and event actions taken are now more consistent and easier to see on an event's details page.
• The event context page now shows the  linking between related events in greater detail, e.g. stateful opposite events as well as synthetic and suppressed correlated events.
• opEvents now supports Delegated Authentication.
• The Help menu now provides access to MongoDB status information.
• opEvents' CLI tool was streamlined for faster operation if it is used as an event forwarder with act=create_event.

...

• opEvents 2.0.0 requires NMIS 8.5.10G or newer for full interoperability. Please check the Product Compatibility page for details.
• Improved license management user interface
  It's now much easier to delete, restore or selectively import your licenses from your Opmantek.com account into opEvents,
  and reminders about any license conditions being exceeded are presented in a more useful fashion.
• There is a totally new rest-style API for remote event management, complete with an example client and its source.
• Configurable purging of old data from the opEvents database is now supported.
• opEvents provides a new facility for summary reports (created both on demand and periodically), complete with automatic email of reports as XLSX spreadsheet and online display.
• Comments with attribution and timestamps can now be added to nodes and events.
  Anybody who can view an event can also add a comment for it, but only an administrator can delete comments. (Node comments are all admin-only.)
  Comments are shown with the event or node in question, and are tagged with the creation time and originating user. Any URLs in comments are presented as clickable links.
  The older facility for importing and editing notes for nodes still remains.
• More user-friendly new landing and overview page at "http://<yourserver>/omk".
• Improved interactivity due to better database connection caching
  opEvents now keeps its connections to MongoDB open and reuses them as much as possible, which improves interactivity especially if you use a remote MongoDB server.
• New Node Overview screen
  There is a new node-centric dashboard or overview screen which shows events and event types for a node over time. Links between this node overview and the node context allow easy navigation.
• Various GUI improvements and  refinements, e.g. more informational window/tab titles.
• Improved NMIS importing now also covers opHA-poller nodes, and access to interfaces' ifAlias property
  Importing or refreshing  nodes from NMIS now handles nodes on remote poller instances if opHA is active on the opEvents server. Event action rules can now access an interface's Description or ifAlias property.
• Events can now include links to other "authoritative sources", e.g. external applications like helpdesk systems or the like.
  (See the documentation about authority and location properties in the list of Normalised Event Properties for details.)
• Node editing actions are now logged with timestamp and originating user in logs/audit.log
• Improved access control, better NMIS authentication integration
  opEvents now fully enforces access control based on a user's group memberships: only those nodes and events are visible, where the nodes are members of groups that this user is authorized to see.
  The installer now also offers to merge NMIS and Opmantek users.dat password files.
• Better logging and log-rotation support
  opEvents now logs to log/opEvents.log and the log format and content was revised to make the logged information more useful. Logs are reopened when the opeventsd receives a SIGHUP signal.
• opEventsd now restarts automatically when any relevant configuration files change.
  opEventsd now can be instructed to also restart periodically, using the new opeventsd_max_cycles configuration directive (= restart after so many opeventsd_update_rate intervals).

...

• This version interoperates fully with NMIS 8.5.10G, and requires at least this version of NMIS to be installed. Please check the Product Compatibility page for details.
• opEvents now works with MongoDB 2.4, 2.6 and 3.0.
• The Help/About screen shows more useful information, including a note about new releases. The window titles and icons have been updated.
• If installed together with opConfig or opAddress, then opEvents now provides links to node-related dashboards in those products  when possible.

...

opEvents 1.2.3 was released on 24 Nov 2014.

• This version includes a helper for setting up MongoDB for Opmantek use, and the installer offers to run the helper on installations and upgrades.
• opEvents now supports per-node licensing and activation: nodes can be marked disabled from within the GUI, in which case the node does not count for license limits and no events are handled for this node. By default all nodes are active.
• The node configuration infrastructure in opEvents is now fully unified and shared with opConfig.
• Renaming nodes in opEvents now also renames all past events for that node.
• opEvents now includes a full-featured command line tool for node administration, bin/opnode_admin.pl . This tool implements all node management functions already present in the GUI, as well as some extras to make it suitable for scriptable node creating and editing.
• The ordering of rules in the event action and parsing engines was fixed (under certain circumstances rules could be tested in the wrong order in older versions).
• The default event action rules were improved to better collect diagnostic info in reaction to node- and network-related events.
• The event action tag.name(value) has been improved to not clash with internal properties.
• The event action email(recip) has been revised for better standards compliance and interoperability with IP version 6.
• opeventsd.pl now handles inadvertent log replays better. It can be told (with config option opevents_max_event_age) whether older event inputs should be processed or skipped. The handling of missing, malformatted or otherwise indigestible log files was made more robust.
• If no opEvents license is present, then oeventsd.pl starts but doesn't consume any incoming files; it also creates a log entry about  the missing license once every 15 minutes.
• opEvents now supports setting a custom PATH environment for running script/program event actions. If you set the config option opevents_standard_path, then opEvents will set that PATH for all external programs that it runs.
• Opmantek applications can now be selectively enabled using the configuration option load_applications.
• The installer for opEvents was updated to improve robustness and reliability, and opEvents now ships with the Opmantek Support Tool.
• The display of errors and exceptions in the GUI has been improved.
• various minor improvements and bug fixes in both the GUI as well as the back end.
• a small warning: the installer may warn about two "incorrect checksum detected" for two files, if you install this version on top of the Opmantek Virtual Appliance version 8.5.6G or after other Opmantek applications that were released since opEvents 1.2.3. These warnings are benign and you can safely confirm that the installer is allowed to 'overwrite' those files.

...