1 |
<HTML> |
<HTML> |
2 |
<HEAD> |
<HEAD> |
3 |
<!-- $Id$ --> |
<!-- $Id$ --> |
4 |
<TITLE>Proposal for monit 3.0</TITLE> |
<TITLE>Proposal for monit 4.0</TITLE> |
5 |
<link rel="stylesheet" title="Default" type="text/css" href="monit.css"> |
<link rel="stylesheet" title="Default" type="text/css" href="monit.css"> |
6 |
</HEAD> |
</HEAD> |
7 |
|
|
50 |
<b><u>Feature list:</u></b><p><br> |
<b><u>Feature list:</u></b><p><br> |
51 |
|
|
52 |
<ol> |
<ol> |
|
<li><b>Configure monit from different sources.</b><p> In a situation |
|
|
where a monit daemon runs on several machines (server farm) it can be |
|
|
usefull to have each monit daemon read its configuration from a |
|
|
central repository. This allows for easy maintenance since there is |
|
|
only one configuration set.<P> The word 'different' in the title means |
|
|
that it should be possible to use different types of external sources |
|
|
(like LDAP, SQL, etc. or todays plaintext file). The main goal is to |
|
|
allow all monit instances to be configured centrally (and to allow |
|
|
users to choose the preferred type of configuration source). |
|
|
<p> |
|
|
<code> |
|
|
<table border=0 cellspacing=5> |
|
|
<tr> |
|
|
<td width=50%>Responsible:</td><td width=50%>Martin</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td width=50%>Progress:</td> <td width=50% bgcolor="#00aaaa" |
|
|
align=center><b><font color=#ffffff>20%</font></b></td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td width=50%>Importance:</td><td width=50%>MEDIUM</td> |
|
|
</tr> |
|
|
</table> |
|
|
</code> |
|
|
<br> |
|
|
<p> |
|
|
|
|
53 |
|
|
54 |
<li><b>Monitoring file systems and devices.</b><p> |
<li><b>Monitoring file systems and devices.</b><p> |
55 |
|
|
103 |
</code> |
</code> |
104 |
<br> |
<br> |
105 |
<p> |
<p> |
106 |
|
<li><b>Execute programs via the <i>alert</i> statement.</b><p> |
107 |
|
This functionality will allow you to start any program in an alert |
108 |
|
statement, like so: |
109 |
|
|
110 |
<li><b>Central monitoring application.</b><p>If monit is installed and |
<pre> |
111 |
runs on many machines it can be usefull to have one application which |
alert "/usr/bin/snpp -m "Monit: $EVENT for $PROGRAM on $HOST" rladams" |
112 |
will report the status on all machines by querying with each monit |
</pre> |
|
daemon instance. |
|
|
<p> |
|
|
The idea is that by looking at one application you can get an overview |
|
|
of the status on every machine running a monit daemon. This |
|
|
application will also show statistical and historical data for each |
|
|
machine. |
|
113 |
|
|
114 |
<p>This application will either be implemented with a HTML GUI or with |
and because the alert statement is associated with events you may even |
115 |
a GTK GUI. |
be more specific, like so: |
116 |
|
|
117 |
|
<pre> |
118 |
|
alert "/bin/program" on { checksum } |
119 |
|
</pre> |
120 |
|
|
121 |
|
This version of the alert statement is going to be a "fire-and-forget" |
122 |
|
operation. That is, you cannot check the return value from the script |
123 |
|
and do stuff like this |
124 |
|
<pre> |
125 |
|
if alert "myprogram" > 0 then |
126 |
|
do stuff |
127 |
|
else |
128 |
|
do other stuff |
129 |
|
</pre> |
130 |
|
Never the less we think this will cover most of the need for calling |
131 |
|
programs outside monit without implementing a regular pluggin |
132 |
|
architecture, which we really do not want to implement. |
133 |
|
</pre> |
134 |
<p> |
<p> |
135 |
<code> |
<code> |
136 |
<table border=0 cellspacing=5> |
<table border=0 cellspacing=5> |
138 |
<td width=50%>Responsible:</td><td width=50%>Jan-Henrik</td> |
<td width=50%>Responsible:</td><td width=50%>Jan-Henrik</td> |
139 |
</tr> |
</tr> |
140 |
<tr> |
<tr> |
141 |
<td width=50%>Progress:</td> <td width=50% bgcolor="#0000aa" |
<td width=50%>Progress:</td> |
142 |
align=center><b><font color=#ffffff>0%</font></b></td> |
<td width=50% bgcolor="#0000aa" align=center><b><font color=#ffffff>0%</font></b></td> |
143 |
</tr> |
</tr> |
144 |
<tr> |
<tr> |
145 |
<td width=50%>Importance:</td><td width=50%>MEDIUM</td> |
<td width=50%>Importance:</td><td width=50%>HIGH</td> |
146 |
</tr> |
</tr> |
147 |
</table> |
</table> |
148 |
</code> |
</code> |
149 |
<br> |
<br> |
150 |
<p> |
<p> |
151 |
|
|
|
|
|
152 |
</ol> |
</ol> |
153 |
|
|
154 |
</TD> |
</TD> |