29 |
<div style="background: #EFF7FF; padding: 10px;"> |
<div style="background: #EFF7FF; padding: 10px;"> |
30 |
<b>Done</b> |
<b>Done</b> |
31 |
<ul style="list-style-type: square;"> |
<ul style="list-style-type: square;"> |
32 |
<li>Currently none</li> |
<li>Allow formating of trailing event description sent in an alert email</li> |
33 |
</ul> |
</ul> |
34 |
<b>In progress</b> |
<b>In progress</b> |
35 |
<ul style="list-style-type: square;"> |
<ul style="list-style-type: square;"> |
38 |
<b>Planned</b> |
<b>Planned</b> |
39 |
<ol> |
<ol> |
40 |
<li><a href="#23">Improve monit responsiveness when stopping a program</a></li> |
<li><a href="#23">Improve monit responsiveness when stopping a program</a></li> |
|
<li><a href="#03">Allow formating of trailing event description sent in an alert email</a></li> |
|
41 |
<li><a href="#32">Customize monit log file output</a></li> |
<li><a href="#32">Customize monit log file output</a></li> |
42 |
|
<li><a href="#03">Event traceback</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> |
118 |
<table id="feature"> |
<table id="feature"> |
119 |
<tr> |
<tr> |
120 |
<td colspan=2> |
<td colspan=2> |
121 |
<h3><a name="03">Allow formating of trailing event description sent in an alert email</a></h3> |
<h3><a name="03">Event traceback</a></h3> |
122 |
|
|
123 |
The Event description sent with each alert mail, at the |
Refactor the internal message passing conducted inside validate.c |
124 |
bottom of the email, is currently added to every alert |
to make code more flexible and to allow protocol routines to |
|
mail regardless of the MAIL-FORMAT. This should be changed |
|
|
so users have complete control on the format of alert |
|
|
messages emitted by monit. Suggested formate variable is |
|
|
$EVENT_DESCRIPTION. |
|
|
|
|
|
<p> |
|
|
A spin-off from this request is to refactor the |
|
|
internal message passing conducted inside validate.c to |
|
|
make code more flexible and to allow protocol routines to |
|
125 |
pass detailed error-messages upwards so they are part of |
pass detailed error-messages upwards so they are part of |
126 |
the alert message. Having a kind of chained exception |
the alert message. Having a kind of chained exception |
127 |
traceback would be nice. Something like, |
traceback would be nice. Something like, |
|
</p> |
|
128 |
|
|
129 |
<pre> |
<pre> |
130 |
Event backtrace: |
Event backtrace: |