Servers¶

There are two different ways to monitor a server:

• Service

A connection will be made to the entered ip or domain, on the given port. This way you can check if certain services on your machine are still running. To check your IMAP service for example, enter port 143.

• Website

You can enter a link to a website, it will then use cURL to open the website and check the HTTP status code. If the HTTP status code is in the 4xx range, it means an error occurred and the website is not accessible to the public. You can also set a regular expression to match for content on the page itself. If the regular expression returns no matches, the website is considered down. In both cases the script will return a “status offline”, and will start sending out notifications.

Notifications¶

Each server has its own settings regarding notification. You can choose for email notification or text message (SMS). The following SMS gateways are currently available:

• Mollie - <http://www.mollie.nl>
• Spryng - <http://www.spryng.nl>
• Inetworx - <http://www.inetworx.ch>
• Clickatell - <https://www.clickatell.com>
• Mosms - <http://www.mosms.com>
• Textmarketer - <http://www.textmarketer.co.uk>

Please note: for these gateways you will need an account with sufficient credits.

Upload files¶

The first step is to upload your files to your webserver where you can reach them. You can rename the folder of the server monitor without any problems.

Run install.php¶

You can now run the install.php script located in the root dir.

The install script will guide you through setting up your configuration file and create the required database tables. If for some reason you can not generate your configuration file, you can do it manually using the steps below. Rename the config.php.sample file to config.php, then open the config.php file with a plain text editor such as Notepad. In this file you need to change the database information, which is stored using php’s define() function. To change these values correctly, only update the second parameter of the function:

define('PSM_DB_HOST', 'db_host');
define('PSM_DB_NAME', 'db_name');
define('PSM_DB_USER', 'db_user');
define('PSM_DB_PASS', 'db_user_password');

For example: to change your username you should ONLY change the ‘db_user’ part. Do NOT remove the quotes around your username as that will result in an error. After you have created the config.php, run the install.php again to create the database structure.

Configure your installation¶

Open the main page of the server monitor, by simply navigating to index.php. In the menu on the top find “Config”, it will open a page where you can change the necessary information for your tool.

From 2.0¶

The structure of the project has changed quite a bit since 2.0, but if you have not made any local changes the upgrade is quite easy. The best thing to do is to replace all your current files with the new release, except for the config.inc.php file. The config file has actually been renamed since 2.0, but if you keep it there while upgrading the install script will use it to prefill your database information. The rest of the steps are identical to a regular upgrade (see above), except that you can remove the old config.inc.php file afterwards.

From 2.1¶

One of the new features introduced in 3.0 is a user authentication system. Because the users in previous versions do not have a password, after upgrading you would not be able to login. For that reason the upgrade script will ask you to create a new account during the upgrade, which you can then use to change the password for the existing accounts. If, for whatever reason this does not work, the upgrade script automatically changes the username of all existing users to their email addresses, which you could use for the forgot password screen.