2 |
monit Bugs and To-Do Items |
monit Bugs and To-Do Items |
3 |
------------------------------------------------------------------ |
------------------------------------------------------------------ |
4 |
|
|
|
TODO: |
|
|
|
|
|
1.) Timeout statement will be extended to provide generic framework for error |
|
|
ratio driven timeout. New syntax: |
|
|
|
|
|
if NUMBER EVENT within NUMBER cycles then timeout |
|
|
|
|
|
where: |
|
|
|
|
|
EVENT ... supported events (such as restart|timestamp|size|checksum|...) |
|
|
NUMBER ... integer |
|
|
|
|
|
It will be possible to let the service timeout (and don't flood the user |
|
|
with error messages) after specified limit is reached, such as: |
|
|
|
|
|
if 5 timestamp within 5 cycles then timeout |
|
|
if 3 restart within 5 cycles then timeout |
|
|
|
|
|
Following example is alternative to unmonitor action, with the exception |
|
|
that generic timeout is not inherited by dependants: |
|
|
|
|
|
if failed checksum then alert |
|
|
if 1 checksum within 1 cycle then timeout |
|
|
|
|