Table of Contents | ||||
---|---|---|---|---|
|
...
This is a brief overview of the major changes between opEvents releases.
opEvents 2.6.5
28 July 2021 Status subtle true colour Green title Released
Bug Fixes
- Fixed issue with Radius Authentication.
opEvents 2.6.4
14 April 2021 Status subtle true colour Green title Released
Bug Fixes
- Fixed issue in opEvents where a large amount MongoDB connections were created and retained.
...
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
...
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
...