Re: [Q] Alert string

[Christian Hopp]

On Wed, 30 Apr 2003, Jan-Henrik Haukeland wrote:


> I just got an email off-list from a Mike Long (a mailinglist digest
> subscriber) where he says:
>
>   [..] might it not be more intuitive to use backticks to mean command
>   as in
>
>   alert `/bin/program` on { checksum }

It's so easy. (-:


> I like this suggestion and think it's a good idea. So unless anyone
> disagree? .. to summarize: The syntax for executing an arbitary
> program via an alert statement will be:
>
>                        ALERT COMMAND [{events}]
>
> where COMMAND is a string enclosed by backticks. An example:
>
>  alert `/usr/bin/snpp -m "Monit: $EVENT for $PROGRAM on $HOST" rladams`
>
> Where $EVENT, $PROGRAM, $DATE and $HOST can be used as variables in
> the command string and will be expanded as usual/follows:
>
> $EVENT A string describing the event that occured. The values are
> fixed and are, ``restarted'', ``timed out'', ``stopped and ''checksum
> error``

btw... start should be an alert, too.

> $PROGRAM The program entry name in monitrc
>
> $DATE The current time and date (C time style).
>
> $HOST The name of the host monit is running on

and

  $REPORT


Wouldn't it be consitent with this syntax to write,

  START COMMAND
  STOP  COMMAND

or

  ALERT COMMAND {[start|stop]}

instead of

  START PROGRAM = STRING
  STOP  PROGRAM = STRING

???


C.Hopp

-- 
Christian Hopp                                email: address@hidden
Institut für Elektrische Informationstechnik             fon: +49-5323-72-2113
TU Clausthal, Leibnizstr. 28, 38678 Clausthal-Zellerf.   fax: +49-5323-72-3197
                             pgpkey: https://www.iei.tu-clausthal.de/pgp-keys/