Home /  MMonit /  Release 3-2

Released on May 02, 2014

Changes | New installation | Upgrading | Known Issues

Changes

  • New: Performance optimizations: M/Monit should now in theory be able to scale very well even on modest hardware. The User Interface is also improved with regards to performance. In particular, admin/alert and admin/host groups. This is a rather big internal refactoring and we would be interested in any feedback.
  • New: Support for custom range in the Uptime Report
  • New: When Host status table is sorted on led, also sort on host name. I.e. hosts with same led color are sorted on name. MMONIT-707
  • New: The drill-down filter in the hosts status page is now made persistent. This is especially useful if a filter was set and when you go into hosts details and then back again, the table remains the same. To make it more manageable to work with many hosts, it is also recommended to divide hosts into host groups. You can then use the drill-down menu to filter on hosts groups and work and switch between a sub-set of hosts in the status page which is much more snappy compared to working with a large table of hundred or thousands of hosts.
  • New: Minimize UI chrome in Safari on iOS 7.1
  • Fixed: A potential host group inconsistency after M/Monit restart could lead to a problem deleting host groups
  • Fixed: M/Monit could crash under certain circumstances if a Monit service's every statement was switched from a cycle format to a cron format
  • Fixed: Adding an event comment could fail with a memory error under certain circumstances
  • Fixed: A sporadic deadlock which could happen if a new host was created while statistics save were pending and the status page were loaded at the same time
  • Fixed: Calculation of minimum, average and maximum values in the analytics page was off if there were gaps in the dataset
  • Fixed: Events Page: make host group, service group and paginator persistent across page reloads
  • Fixed: Upgrade script now copies 3rd party conf/ subdirectories too.

New installation

  • Download the release for your OS.
  • Unpack the tar.gz file in a directory, any directory will do, but unpacking in /opt or /usr/local are good choices.
  • Go to the unpacked mmonit-3.2 directory
  • Run M/Monit using: ./bin/mmonit
  • Point your Browser to the host where mmonit is installed (or "localhost" if running on the same machine), for example: http://localhost:8080/ and login as user "admin" with password "swordfish"
  • If you want to setup M/Monit to use MySQL or PostgreSQL instead of the default SQLite database, follow these instructions in the wiki.
  • More documentation can be found inline in the application and in the manual (PDF).

Upgrading from previous M/Monit releases (2.3 or later)

The upgrade program can be used to automatically copy database and configuration files from the previous installation and update the database schema.

The whole upgrade process should take less than a minute and you do not have to stop or change Monit on other machines during this process. Monit will simply pick up and start reporting to the new M/Monit 3.2 version.

  • Download the new 3.2 release for your OS.
  • Install M/Monit 3.2 in the same directory as previous release. For example: 
 /usr/local/mmonit/mmonit-3.1.3
 /usr/local/mmonit/mmonit-3.2
  • Stop previous M/Monit release: 
 /usr/local/mmonit/mmonit-3.1.3/bin/mmonit stop
  • Run the upgrade program and specify path to the previous M/Monit release: 
 /usr/local/mmonit/mmonit-3.2/upgrade/upgrade -p /usr/local/mmonit/mmonit-3.1.3
  • Start M/Monit 3.2: 
 /usr/local/mmonit/mmonit-3.2/bin/mmonit
  • Finally, clear your browser cache before accessing M/Monit 3.2

Known Issues

  • Status Page: Entering a search phrase in the Host Search field will show a table with all hosts if the phrase does not match any hosts. The correct behaviour would be to show an empty table. However, if the search term match one or more hosts, only those hosts are shown, which is correct.