op5 monitor 7.2.2 – Release Notes

op5 Monitor 7.2.2 Release Notes

We have released op5 Monitor 7.2.2. This release includes new features and fixes for bugs discovered in op5 Monitor 7.2.1. You can see the full list in this blog post.

Product: op5 Monitor
Release Number: 7.2.2
Release Date: May 17, 2016

Release Type: Micro
Previous Release: 7.2.1

What’s new

  • Improved text readability in in-browser information messages.
  • Improved display of large (99+) numbers in the recently released summary state widget.
  • The order of thresholds in the help text for mon check exectime has been corrected.
  • The mon db cahash command line function has been removed, since it hasn’t been in use since 2014.
  • Fixed an issue with file system permissions on files related to Business Services. The issue could cause an upgraded system to restore previously deleted Business Service objects.
  • Fixed an issue that could occur when a poller had a newer object configuration timestamp than the master. In that case, the master would consider the poller inactive and refuses to accept any check results from it.
  • Moved the responsibility of network communication from the Merlin daemon to the Merlin module. This makes it easier for op5 Monitor nodes to fulfil all the criteria to be members of an active cluster, which results in a more resilient system. it has also allowed us to optimize distribution of configuration changes to members of a op5 Monitor cluster by only sending new configuration to nodes affected by the changes.
  • Improved testing of the Merlin component (responsible for clustering), for better quality assurance.
  • A version number is now sent when two op5 Monitor nodes establish a connection. This paves way for future improvements aiming to make upgrading systems with multiple op5 Monitor nodes easier.
  • Fixed an issue where removed/renamed materialized service could render the Business Services interface blank.
  • Fixed an issue which caused the check_interval setting to be used instead of the retry_interval setting if retry_interval was set higher than check_interval
  • Fixed an issue where a op5 Monitor master node might not trigger new config push to all peers and pollers.
  • Added the possibility for NEB modules to provide more granular callback results. This feature which makes it easier to provide the end user with troubleshooting information in the case of notification suppressions.

Known Issues

  • None

How to upgrade

Click the update notification in the op5 Monitor web interface, use yum update on the command line or download the latest tarball for offline installation.

Feedback

If you have any questions surrounding this micro release, you are more than welcome to get in touch with us.

 

Try op5 Monitor Enterprise+

Download full 30 day trial version, including all features, API and op5 App support.

Download op5 Monitor