Page History

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

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 executed.

opEvents 2.6.1

Released 22nd December 2020

New feature which shows Programmable Action Buttons on events which operators to execute EventsActions scripts from the event context screen.

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' ],
  
  Image Added

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

This is a maintenance release.

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

opEvents 2.4.5

published 23 January 2020

Feature

• This release was primarily focused around releasing the new Opmantek Installer with improved systemd support.

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

Feature

• opevents_gui_event_context_summary_list now supports deeply nested keys
  • example: nodeinfo.location

opEvents 2.4.3

published 3 April 2019

Features

• 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

opEvents 2.4.2

This major release of opEvents introduces several new features and bugfixes, published 1 November 2018

 opEvents 2.4.2 minimum MongoDB version is 3.2

• 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 2.4.1

This maintenance release of opEvents was published on 2 Nov 2017.

...

• 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

...