Released on December 9, 2013
- Fixed: A problem with infrequent timeout request from Monit to M/Monit on slow/high-latency networks. M/Monit will now wait for up to 30 seconds on data from Monit compared to 3 sec before. The <Connector> attribute, connectionTimeout in server.xml controls the wait timeout and can be set to a higher value if required.
- New: Failed login attempts are now logged to mmonit/logs/error.log with a timestamp, IP-address and URL.
- New: Automatic purging of events and analytics data. See settings in the Admin/General page.
- New: A new switch in the admin/hosts page controls if Monit should automatically update the hostname or not.
- Fixed: Slow startup when M/Monit manage a large number of hosts.
- Fixed: Search fields and results are made more responsive
- New: Support for presetting drill-down via URL parameters, led=<id>, hostgroup=<id> and host=<name>. For instance: http://localhost/status/hosts/?led=2
- New: Upload photo of users, from desktop or mobile.
- New: Alert reminder option added
- New: Limit alert messages by events count
- Fixed: Port response chart label
- Fixed: Week range date format changed to MMM DD
- Fixed: Fewer X-axis ticks on phone
- Fixed: Increase analytics query timeout from 5s to 30s to support larger data sets
- Fixed: Performance improvements
- Fixed: Improved correctness.
- New: Show monit downtime in the service uptime page.
- Fixed: Persistent Uptime range between the hosts and services page
- Fixed: Hide date menu if click outside
- Plus many more smaller improvements and fixes.
- 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.1 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 M/Monit 3.0 (the previous version)
An upgrade script is provided and can be used to automatically update the database schema and copy configuration files from the previous installation. All your data is kept.
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.1 version.
- Download the new 3.1 release for your OS.
- Install M/Monit 3.1 in the same directory as 3.0. For example:
- Stop M/Monit 3.0:
- Go to the M/Monit 3.1 directory:
- Run the upgrade script:
./upgrade/upgrade-3.0-3.1.sh -t [sqlite|mysql|postresql]
If you are using SQLite, you can basically run the following to update:
./upgrade/upgrade-3.0-3.1.sh -t sqlite
If you are using MySQL or PostgreSQL run the upgrade script with -h to see all options.
- Start M/Monit 3.1:
- Finally, please clear your browser cache before accessing M/Monit 3.1.
Known Issues in version 3.1
- Jabber Alerts: [Send instant message to user]: M/Monit wrongly use the users email address instead of the users IM account address when sending Jabber/GTalk alerts. Workaround: Select [Send instant message to address] instead and specify the address manually.