RE: Email alert formating

[Rishikesh Dongre]

Hi,

The same query has modified as -

----Start here----
check device tmp-10 path /tmp
   if space usage > 10% for 6 cycles then exec "/usr/bin/ksh /tmp/mailmsg10"
   alert address@hidden
----End----

I supposed, this query should wait for 6 cycles and then execute the script and 
every after 6 cycles. But it does for each cycle.
Secondly, is it possible to execute the script with any alert action.

Thanks,
rishi


-----Original Message-----
From: Martin Pala [mailto:address@hidden
Sent: Wednesday, November 30, 2005 2:30 PM
To: This is the general mailing list for monit; Rishikesh Dongre
Subject: Re: Email alert formating


Rishikesh Dongre wrote:
> A question -
> Is it possible to have two different email format, one for "Resource limit 
> matched" and another for "Resource limit passed"?

No

> I have defined following in my /etc/monit.conf file - 
> ----Start here----
> check device tmp-85 path /tmp
>    start program = "/usr/local/monit-4.6/bin/monit -c /etc/monit.conf monitor 
> tmp-80"
>    stop program = "/usr/local/monit-4.6/bin/monit -c /etc/monit.conf 
> unmonitor tmp-80"
>    if space usage > 85% then stop else if passed then start
>    if inode usage > 85% then stop else if passed then start
>    alert address@hidden on { resource, match } with mail-format { subject: ** 
> ATTENTION ***** Monit Alerts -- $EVENT /tmp filesystem > 85% on $HOST*****
>    message: /tmp filesystem is 85% full. Please FREE Up Space IMMEDIATELY.
> 
>       Date   : $DATE
>       Action : Alert
>       Host   : $HOST
> 
> Your faithful employee,
> Monit } with reminder on 1 cycles
> ----End----
> 
> But when I checked the status, Alert reminder sets to 589328 cycles even it 
> is defined to 1 cycle.

You are right - it seems that there is some bug ... i will look on it.

> And on passing resource limit, 
> I received "Resource limit passed" email also which i dont want or want to 
> set some other message. Becasue when it passed, I am getting the same message 
> like /tmp filesystem is 85% full.

I think this could be solved internaly by adding the description to the 
passed event emited by the testing machine (similary to the failed state 
description). The $DESCRIPTION macro will then provide better message on 
'passed' state.

Martin
 
This email with all infomation contained herein or attached hereto may contain 
confidential and/or privileged information intended for the addressee(s) only. 
If you have received this email in error, please contact the sender and 
immediately delete this email in its entirety and any attachments thereto.
 
This email with all information contained herein or attached hereto may contain 
confidential and/or privileged information intended for the addressee(s) only. 
If you have received this email in error, please contact the sender and 
immediately delete this email in its entirety and any attachments thereto.