11 |
From monit 3.2 to monit 4.0: |
From monit 3.2 to monit 4.0: |
12 |
=========================== |
=========================== |
13 |
|
|
14 |
* The DEPENDS statement has been changed. The services are from now |
|
15 |
on comma separated: |
* The PORT statement has changed and now requires that an explicit |
16 |
|
action is specified if the connection test should fail. The old |
17 |
|
statement would blindly restart the service if a port connection |
18 |
|
test failed, the new version allows you to choose an action from |
19 |
|
the set, ALERT, STOP, RESTART or EXEC. |
20 |
|
|
21 |
|
Old syntax: [HOST hostname] PORT number [TYPE {...}] |
22 |
|
[PROTO(COL) {name} [REQUEST {"/path"}]] |
23 |
|
|
24 |
|
New syntax: if faild [HOST hostname] PORT number [TYPE {...}] |
25 |
|
[PROTO(COL) {name} [REQUEST {"/path"}]] |
26 |
|
[with TIMEOUT AFTER x SECONDS] |
27 |
|
then action |
28 |
|
|
29 |
|
|
30 |
|
|
31 |
|
* The DEPENDS statement has changed. The services are from now on |
32 |
|
comma separated: |
33 |
|
|
34 |
Old syntax: DEPENDS service [service [...]] |
Old syntax: DEPENDS service [service [...]] |
35 |
|
|
36 |
New syntax: DEPENDS service[, service [,...]] |
New syntax: DEPENDS service[, service [,...]] |
37 |
|
|
38 |
|
|
39 |
|
|
40 |
* Monit 4.0 supports file, device and directory checks in addition to |
* Monit 4.0 supports file, device and directory checks in addition to |
41 |
process checks. Thus, the CHECK statement has been changed: |
process checks. Thus, the CHECK statement has been changed: |
42 |
|
|
57 |
MEMUSAGE value [cycles] action |
MEMUSAGE value [cycles] action |
58 |
MEMKBYTE value [cycles] action |
MEMKBYTE value [cycles] action |
59 |
|
|
60 |
New syntax: CPU operator value unit [cycles] action |
New syntax: if CPU operator value unit [cycles] then action |
61 |
MEM operator value unit [cycles] action |
if MEM operator value unit [cycles] then action |
62 |
|
|
63 |
The "operator" token is still a choice of {<|>|==|!=} or in words |
The "operator" token is still a choice of {<|>|==|!=} or in words |
64 |
{less|greater|equal|notequal}; value is a choice of an integer |
{less|greater|equal|notequal}; value is a choice of an integer |
65 |
number or a real number (using a dot); unit is {%|PERCENT} for CPU |
number or a real number (using a dot); unit is {%|PERCENT} for CPU |
66 |
and a choice of {%|B|KB|MB|GB} or in words {PERCENT|BYTE|KILOBYTE| |
and a choice of {%|B|KB|MB|GB} or in words {PERCENT|BYTE|KILOBYTE| |
67 |
MEGABYTE|GIGABYTE}; "cycles" refers still the number of cycles the |
MEGABYTE|GIGABYTE}; "cycles" still refers to the number of cycles |
68 |
statement has to be true in order to start the "action". Example: |
the statement has to be true in order to start the "action". |
69 |
|
Example: |
70 |
|
|
71 |
MEM > 2.5 MB 5 RESTART |
if MEM > 2.5 MB for 5 cycles then RESTART |
72 |
MEM > 25% 3 RESTART |
|
73 |
|
And not specifying a cycle means implicit 1 cycle: |
74 |
|
if MEM > 25% then RESTART |
75 |
|
|
76 |
The old syntax using CPUUSAGE, MEMUSAGE, MEMKBYTE is obsolete and |
The old syntax using CPUUSAGE, MEMUSAGE, MEMKBYTE is obsolete and |
77 |
no longer supported. |
no longer supported. |
78 |
|
|
79 |
|
|
80 |
|
|
81 |
* $PROGRAM tag of statement mail-format was renamed to $SERVICE |
* $PROGRAM tag of statement mail-format was renamed to $SERVICE |
82 |
without changing its meaning. $PROGRAM is still usable but |
without changing its meaning. $PROGRAM is still usable but |
83 |
depreciated. Future versions might not support it anymore. |
depreciated. Future versions might not support it anymore. |