Re: comments from freshmeat

[Jan-Henrik Haukeland]

Martin Pala <address@hidden> writes:

> In the past we discussed model based on event per cycle ratio, like
> this:
>
>  if X EVENT(S) within Y cycles then ACTION
>
> where:
>
>  X ... number of event occurences
>  EVENT ... type of event, like 'timestamp', ,size', 'checksum',
>  'connection', etc.
>  Y ... cycles count
>  ACTION ... what to do, like 'restart', 'unmonitor', 'alert', etc.
>
> Usage example:
>
>  if cpu > 50% then alert # will send alert on first cpu related
>  'resource' event occurence
>  if 5 resource within 5 cycles then exec "/do/something"  # do
>  something if the problem remains for 5 cycles
>  if 10 resource within 20 cycles then restart # restart the service if
>  the problem ratio exceeds 10 occurence within 20 cycles
>
> This way it could be possible to stack actions based on error
> severity (soft/hard/whatever).
>
> Maybe in the future such feature could be implemented - what do you
> think?

it's not a bad idea and if you should want to give it a try (in the
future) I would absolutely not vote against it, but for my part it
would not be high up on the agenda :)

-- 
Jan-Henrik Haukeland