Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added link to compatibility matrix page

...

8.5.10G is a major release with lots of bug fixes and substantial other changes, the biggest being greatly improved support for service monitoring (which is described in more detail on this page).
Please note that for full interoperability with NMIS 8.5.10G some Opmantek applications must be upgraded after you upgrade NMIS. Further details are available on the Product Compatibility page.

Service Monitoring

  • NMIS service monitoring is now compatible with Nagios plugins: you can use any (standalone) Nagios plugin to monitor your service. NMIS will even collect and store any "performance data" that the plugin might return.
  • There is a new screen called "Monitored Services" which briefly displays a brief overview of all services your NMIS server monitors. It is reachable from the "Service Desk" and "Network Status" menus.
  • For each service there is also a new detailed view with recent status graph, overview of the latest readings (both standard and custom) and links to any custom graphs.
  • Program-based service tests (incl. Nagios) can now report a textual service status which is shown on the new service screens.
  • The polling period for service definitions now works as intended (but at this time service graphs will only work if the polling interval is set to less than 15 minutes).
  • NMIS now supports custom graphs for services: program-based services could already optionally return numeric data and NMIS would collect and store that data, but NMIS didn't support custom graphs for such extra measurements. With version 8.5.10G NMIS will detect the presence of such custom graphs and offer them where applicable.
  • NMIS now comes with a comfortable menu-based graph maker for such custom graphs.
    The tool is available as "admin/service_graph_helper.pl" and interactively guides you through the process of creating a custom graph for your particular service.
  • Service states are now more granular: up, down are as before and "degraded" was added. Any service whose status is above 0 (=down) and below 100 (=up) is considered degraded. Degraded services are displayed with different colors.
  • NMIS now emits more detailed events for service status changes: a new event "Service degraded" was added and all service-related events carry the optional textual status of the service.
  • NMIS ships with a number of new service monitoring example programs in "install/scripts/".

...