39 |
<ol> |
<ol> |
40 |
<li><a href="#01">Refactor SMTP support</a></li> |
<li><a href="#01">Refactor SMTP support</a></li> |
41 |
<li><a href="#02">Refactor the CVS repository and release tree</a></li> |
<li><a href="#02">Refactor the CVS repository and release tree</a></li> |
42 |
|
<li><a href="#03">Allow formating of trailing event description sent in an alert email</a></li> |
43 |
<li><a href="#06">URL request for protocol tests (like ldap, ftp, etc.)</a></li> |
<li><a href="#06">URL request for protocol tests (like ldap, ftp, etc.)</a></li> |
44 |
<li><a href="#07">Network interfaces health and load monitoring</a></li> |
<li><a href="#07">Network interfaces health and load monitoring</a></li> |
45 |
<li><a href="#08">Device load average tests</a></li> |
<li><a href="#08">Device load average tests</a></li> |
150 |
|
|
151 |
</table> |
</table> |
152 |
|
|
153 |
|
<table id="feature"> |
154 |
|
<tr> |
155 |
|
<td colspan=2> |
156 |
|
<h3><a name="03">Allow formating of trailing event description sent in an alert email</a></h3> |
157 |
|
|
158 |
|
The Event description sent with each alert mail, at the |
159 |
|
bottom of the email, is currently added to every alert |
160 |
|
mail regardless of the MAIL-FORMAT. This should be changed |
161 |
|
so users have complete control on the format of alert |
162 |
|
messages emitted by monit. Suggested formate variable is |
163 |
|
$EVENT_DESCRIPTION. |
164 |
|
|
165 |
|
<p>A spin-off from this request is to refactor the |
166 |
|
internal message passing conducted inside validate.c to |
167 |
|
make code more flexible and to allow protocol routines to |
168 |
|
pass detailed error-messages upwards so they are part of |
169 |
|
the alert message. Having a kind of chained exception |
170 |
|
traceback would be nice. Something like, |
171 |
|
<pre> |
172 |
|
Event backtrace: |
173 |
|
1. 'hostname' failed protocol test [http] at 192.168.1.1 |
174 |
|
2. APACHE-STATUS error: 80 percent of Apache processes are logging |
175 |
|
</pre> |
176 |
|
Currently only the first event line (1.) are sent in the |
177 |
|
alert message. The error in line 2 is logged, but it could |
178 |
|
be nice to include it in the alert message to describe |
179 |
|
<i>why</i> the http protocol test failed. |
180 |
|
|
181 |
|
</td> |
182 |
|
</tr> |
183 |
|
<tr> |
184 |
|
<td width=10% style="padding-right: 20px;"> |
185 |
|
Responsible:</td> |
186 |
|
<td>?</td> |
187 |
|
</tr> |
188 |
|
<tr> |
189 |
|
<td>Progress:</td> |
190 |
|
<td bgcolor="blue" align=center> |
191 |
|
<b><font color=#ffffff>0%</font></b> |
192 |
|
</td> |
193 |
|
</tr> |
194 |
|
<tr> |
195 |
|
<td>Importance:</td><td><b>MEDIUM</b></td> |
196 |
|
</tr> |
197 |
|
</table> |
198 |
|
|
199 |
<table id="feature"> |
<table id="feature"> |
200 |
<tr> |
<tr> |