Page History

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

opEvents 2.2.0a

This pre-release for the next major version was published on 25 Nov 2016. Please contact Opmantek if you would like to test it.

• 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.
• opEvents now supports stateful synthetic events.
• Event Emails now provide better formatting for event script actions and status history.
• Various GUI simplifications and improvements
  • 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.
  • 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).
• 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.
• 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 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.
• And of course various bug fixes and smaller improvements

opEvents 2.0.6

This is a maintenance release of opEvents which was published on 10 Aug 2016.

...