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><a href="#22">Soft failure tolerance for ICMP echo test (ping)</a></li> |
<li>Currently none</li> |
|
<li><a href="#24">Add alert reminder option</a></li> |
|
|
<li><a href="#20">Event ratio dependant action rules</a></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;"> |
36 |
<li><a href="#31">Monitor a (log) file using regex</a></li> |
<li>Currently none</li> |
37 |
</ul> |
</ul> |
38 |
<b>Planned</b> |
<b>Planned</b> |
39 |
<ol> |
<ol> |
119 |
</tr> |
</tr> |
120 |
</table> |
</table> |
121 |
|
|
|
<table id="feature"> |
|
|
<tr> |
|
|
<td colspan=2 > |
|
|
<h3><a name="31">Monitor a file using regex</a></h3> |
|
|
|
|
|
This function will allow monit to monitor files such as log files for certain |
|
|
content. Users can specify a regular expression or files containing regular |
|
|
expressions which will be checked against the file for each monitor cycle. |
|
|
If a match occurs, monit will issue one of the standard actions, such as |
|
|
an alert or a exec as long as it not explicitly ignored. Here is an example |
|
|
on how an entry may look like in the monit control file: |
|
|
|
|
|
<pre> |
|
|
check file syslog with path /var/log/messages |
|
|
if match "^[A-Za-z]+ .[0-9] [0-9][0-9]:[0-9][0-9]:[0-9][0-9].* .* .*$" |
|
|
then alert |
|
|
ignore match "^[A-Za-z]+ .[0-9] [0-9][0-9]:[0-9][0-9]:[0-9][0-9].* monit.* .*$" |
|
|
if match /etc/monit/monit.match.use then alert |
|
|
ignore match /etc/monit/monit.match.ignore then alert |
|
|
</pre> |
|
|
|
|
|
<p>Monit will maintain the offset of each file (a la logtail) so it would |
|
|
check only the last entries. The regex check is done per line or per 512 |
|
|
bytes, whichever comes first. |
|
|
|
|
|
</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td width="10%" style="padding-right: 20px;">Responsible:</td> |
|
|
<td>Christian</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td>Progress:</td> |
|
|
<td bgcolor="green" align=center> |
|
|
<b><font color="#ffffff">99.8%</font></b> |
|
|
</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td>Importance:</td> |
|
|
<td><b>MEDIUM</b></td> |
|
|
</tr> |
|
|
</table> |
|
122 |
|
|
123 |
|
|
124 |
<table id="feature"> |
<table id="feature"> |
449 |
<table id="feature"> |
<table id="feature"> |
450 |
<tr> |
<tr> |
451 |
<td colspan=2> |
<td colspan=2> |
|
<h3><a name="20">Event ratio dependant action rules</a></h3> |
|
|
|
|
|
Allows to set stack of rules which will evaluate given |
|
|
action based on specific event occurence (error level).<br> |
|
|
|
|
|
<p> |
|
|
Possible syntax (example): |
|
|
</p> |
|
|
|
|
|
<pre> |
|
|
if X EVENT within Y cycles then ACTION |
|
|
</pre> |
|
|
|
|
|
<p> |
|
|
where:<br> |
|
|
X = number of event occurences<br> |
|
|
EVENT = event type<br> |
|
|
Y = number of consequent cycles<br> |
|
|
ACTION = given action (alert|restart|unmonitor|exec|...)<br> |
|
|
</p> |
|
|
</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td width="10%" style="padding-right: 20px;"> |
|
|
Responsible:</td> |
|
|
<td>Martin</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td>Progress:</td> |
|
|
<td bgcolor="green" align=center> |
|
|
<b><font color="#ffffff">100%</font></b> |
|
|
</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td>Importance:</td> |
|
|
<td><b>MEDIUM</b></td> |
|
|
</tr> |
|
|
</table> |
|
|
|
|
|
|
|
|
<table id="feature"> |
|
|
<tr> |
|
|
<td colspan=2> |
|
452 |
<h3><a name="21">Action list support and optional service name target</a></h3> |
<h3><a name="21">Action list support and optional service name target</a></h3> |
453 |
|
|
454 |
Allows to specify list of actions, optionaly referencing other |
Allows to specify list of actions, optionaly referencing other |
494 |
|
|
495 |
|
|
496 |
<table id="feature"> |
<table id="feature"> |
|
<tr> |
|
|
<td colspan=2> |
|
|
<h3><a name="22">Soft failure tolerance for ICMP echo test (ping)</a></h3> |
|
|
|
|
|
Allows to send more ICMP echo packets in the ping test during one |
|
|
cycle and tolerate partial loss of some packets up to the optional |
|
|
limit. |
|
|
</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td width="10%" style="padding-right: 20px;">Responsible:</td> |
|
|
<td>Martin</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td>Progress:</td> |
|
|
<td bgcolor="green" align=center> |
|
|
<b><font color="#ffffff">100%</font></b> |
|
|
</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td>Importance:</td> |
|
|
<td><b>LOW</b></td> |
|
|
</tr> |
|
|
</table> |
|
|
|
|
|
|
|
|
<table id="feature"> |
|
497 |
<tr> |
<tr> |
498 |
<td colspan=2> |
<td colspan=2> |
499 |
<h3><a name="02">Refactor the CVS repository and release tree</a></h3> |
<h3><a name="02">Refactor the CVS repository and release tree</a></h3> |
520 |
</td> |
</td> |
521 |
</tr> |
</tr> |
522 |
<tr> |
<tr> |
|
<td>Importance:</td> |
|
|
<td><b>LOW</b></td> |
|
|
</tr> |
|
|
</table> |
|
|
|
|
|
|
|
|
<table id="feature"> |
|
|
<tr> |
|
|
<td colspan=2> |
|
|
<h3><a name="24">Add alert reminder option</a></h3> |
|
|
|
|
|
Possibility to send reminder in the case that the service |
|
|
remains failed. It should be possible to set the reminder |
|
|
as optional alert feature individualy for each target. When |
|
|
the reminder is omited, monit will by default send just one |
|
|
alert on failure and another after recovery. Example syntax: |
|
|
|
|
|
<pre> |
|
|
set alert foo@bar with reminder on 10 cycles |
|
|
|
|
|
check service ... |
|
|
... |
|
|
alert admin@bar with reminder on 5 cycles |
|
|
alert operator@bar |
|
|
</pre> |
|
|
</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td width="10%" style="padding-right: 20px;">Responsible:</td> |
|
|
<td>Martin</td> |
|
|
</tr> |
|
|
<tr> |
|
|
<td>Progress:</td> |
|
|
<td bgcolor="green" align=center> |
|
|
<b><font color="#ffffff">100%</font></b> |
|
|
</td> |
|
|
</tr> |
|
|
<tr> |
|
523 |
<td>Importance:</td> |
<td>Importance:</td> |
524 |
<td><b>LOW</b></td> |
<td><b>LOW</b></td> |
525 |
</tr> |
</tr> |