You can perform this operation manually using a command such as:
Such a file is named according to this convention:
In this example, "
BlueMind uses standard messaging components (Cyrus Imap, Postfix, nginx, tomcat...) that can be monitored by standard tools.
In addition, APIs allow you to query the server the same way as interfaces and make sure that the BM-Core component runs properly.
The list of BlueMind processes running on the server can be accessed using the command:
Typically, BlueMind-specific processes you can expect to see and are able to monitor are:
The standard processes BlueMind uses include:
BlueMind does not provide SNMP probes. In order to monitor a BlueMind server with SNMP, you must therefore set up monitoring for each service mentioned above manually.
BlueMind's monitoring scripts
To be able to monitor BlueMind services, the package bm-checks must be installed.
Once the package is installed, monitoring scripts become available in the directory /usr/share/bm-checks/.
To use them, run the script bash as you would normally, using cron for instance.
Each script returns a code depending on the status of the BlueMind service:
If an error is detected, a message is returned on the standard output.
The BlueMind components log files can be retrieved in the directory "
To monitor other components the following locations can be used:
BlueMind uses standard system scripts to start and stop services.
The command :"
As mentioned in the sections on integrating BlueMind with third-party applications, BlueMind can be fully script-controlled.
From client APIs (in PHP and Java), you can perform any operation on BlueMind, such as create or modify users, access calendars, add events, etc.