Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated selftest info

...

  •  NMIS can now use ConnectWise's REST API as authentication service.

  • Support for locking out users after N failed logins
    This  is controlled by two new configuration settings: auth_lockout_after (default: 0, ie. no lockout) sets the number of acceptable consecutive login failures, and server_admin (a comma-separated list of email addresses) sets the administrators who are notified by email if a lockout occurs.
    To clear a lockout, an administrator has to select the "reset login count" option in the User editing GUI (System Configuration -> System -> Users).

  • Collect and update times are now collected and graphed for every node
    These can be accessed for an individual node by selecting type "polltime" on the Graph Drill page. An overview is als available in form of the new report type "Collect/Update Time" (both as on-demand/Current and Saved/Historic report).

  • Nodes can now be renamed from the GUI
    This was already possible using the node_admin cli tool; now you can make that change on the Node Editing page.
    All files related to the node are renamed as needed.
  • node name wrapping (for long node names) is now on by default.

  • Colors for the group status displays were updated
    In coarse mode node downs are now shown red. The color graduation was adjusted for better scalability.

  • noncollecting interfaces are now easier to spot

    The 'all interfaces' view now displays interfaces with collect=false with a grey background.

  • The service status display now indicates the service test age with color, and has more flexible display and  navigation options.
    A service that hasn't been checked for longer than 1.5 times its configured service frequency is shown in yellow, or in red if the age is above 2 times the desired frequency.
    There are now links for easier navigation between all service-related screens, and the service selection can be narrowed down to only working or only services with problems.

  • The find tool was improved for better flexibility, the log viewer and many oder widgets  were made more robust
    The find tool now provides links to the nodes or interfaces found.

  • The NMIS Selftest now includes checking all file and directory permissions.
    Invalid file permissions are a relatively common problem. The  selftest checks permissions only once every two hours for efficiency reasons, so you may want to clear the selftest status cache after making permission adjustments (i.e. rm /usr/local/nmis8/var/nmis_system/selftest.json). The admin/fixperms.pl tool resets the selftest status to ensure the next NMIS run rechecks the status, and you can use the "Reset Selftest status" button in the GUI to cause a recheck.

  • New support for separate "display name" properties for both nodes and interfaces
    In the Node Configuration GUI you can now optionally set a "display name" for a node and each of its interfaces.
    If such properties are set they are used instead of the node or interface name when showing the thing in the  GUI.

  • Service-only nodes now have a better default  view

  • The node display screen now shows more uptodate data
    In the past certain entries were only updated when a type=update was performed, not on collect. This has been changed.

  • events can now be closed easily from a node's view
    If the user has admin rights, a small close icon is shown next to each open event for a node. Events closed thus are logged as 'closed from GUI'.

  • The  Network Metrics and Health widget now supports a group limit cutoff
    In environments with huge numbers of group this widget could consume excessive amounts of cpu time. The new option network_summary_maxgroups (default: 30) controls how many groups are shown by default. If the limit is exceeded, a link for an unlimited view is shown.

  • NMIS no longer honors the deprecated option auth_require=false.

...