Page History

...

• 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-slave nodes, and access to interfaces' ifAlias property
  Importing or refreshing  nodes from NMIS now handles nodes on remote slave 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 lotslog/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).

...