Configuration
Before we take a look at the M/Monit web-application let’s take a quick look at M/Monit and Monit configuration. As we mentioned
earlier, Monit must be configured in order to send event and status information to M/Monit. In the future we plan to add zero-conf
capabilities to M/Monit and Monit, but for now you will need to add a few lines to Monit’s configuration file. To learn more about Monit
and Monit configuration, please consult the documentation and configuration examples at Monit’s website.
To setup communication between Monit and M/Monit, add the following statements to the top of each Monit control file, monitrc:
The set eventqueue statement in line 1 is optional, but recommended. It allows Monit to store event messages if connection to "
M/Monit should temporarily be unavailable and retry delivery later. This way, no events will be lost. The slots option can be used to set
a limit on how many events can be stored so the queue will not grow without limits if M/Monit is not available. The size of a queued
message is small (ca. 200 bytes) so the space requirements for, let's say, 1000 queued events is only 200kB.
The set mmonit statement in line 2 specify the URL to be used by Monit for sending messages to M/Monit. The M/Monit URL is
protected, and a username and a password are required to post messages to M/Monit. You can use the username and password of
any valid user in M/Monit. For instance, the default user, “monit” with password “monit”. The host and port in the URL, specify
respectively the IP address of the machine running M/Monit and the port on which M/Monit is listening.
The set httpd statement starting on line 3 allow M/Monit to connect to Monit. Specify the IP-address or host name of the host running
M/Monit, this should be the same address as specified in the set mmonit statement mentioned above.
Finally, in line 6, specify Basic Authentication username and password M/Monit should use to login to Monit.
我的内容管理
展开
