You can already do this, exact as command a cmd or bat that does whatever command you want to execute and a commandline smtp mailer....
 

Dirk.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Passow
Sent: Tuesday, July 06, 2004 4:25 PM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] Alert feature request

I do not think it should necessarily be considered a different action (even though it is a separate physical action).  I think it should be part of the executing.   Execute the command and send the email.  I understand that you may choose not to do this at the moment.   Perhaps you will change your mind prior to v5.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx
Sent: Tuesday, July 06, 2004 9:13 AM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] Alert feature request

 

IF we would make such a feature then it would be that you have ONE WHEN rule with different actions attached to it. 

But for the moment this is not something we will do.

 

 

Dirk.

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Passow
Sent: Tuesday, July 06, 2004 1:54 PM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] Alert feature request

Correct.  However only for the execute options.  Since I would like to be alerted to what was executed.  It would be much easier to add an alert to the execute commands saying Server is down and ___ was executed rather than having to create one alert to execute the command and another to alert me that the command was executed.  I speak not necessarily of my self (since I know what gets executed when) but for my other admins that may not know that on the third down for my website the entire service gets restarted and on the fifth down the entire SERVER gets rebooted.  They could receive an alert saying server down 5 times (or just server down) reboot executed. 

 

I use the above only as an example but should I then change it to not reboot my server until the sixth or seventh down then I would also need to change my alert telling me what was executed.  If this was one option I would need only to change one alert.

 

I realize that to accomplish the above action perhaps a variable will need to be added to hold the executed command for transmission through email.  I think that this feature would be useful to more than just myself.   I think anyone trying to automate most of their simple repairs (restarting of services, etc.) would benefit from knowing what has already been done automatically.   Also those with multiple admins (not being able to figure out why the server is rebooting) would benefit form this as well. 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx
Sent: Sunday, July 04, 2004 12:48 PM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] Alert feature request

 

So you want to have several actions with only one "WHEN" rule?

 

Dirk.

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Passow
Sent: Sunday, July 04, 2004 7:42 PM
To: [EMAIL PROTECTED]
Subject: [SA-list] Alert feature request

I would like to receive an alert when a particular action has taken place.  I know that I can set up separate alerts for this purpose to fire under the same conditions but here is my suggestion.  I alert when my web server is down once.  On the second alert I have it set to reboot my server.  I would like also on the second down for it to tell me Web server down since %y%z restart NT/2K server executed or something similar.  Now I am aware that I can create a second check to alert when down and type that command in myself but what happens when I change my check to reboot on the third time and forget to change my alert check.  It would just be nice to have the execute command also capable of sending an alert that way it is all in one check.

 

Jason Passow

[EMAIL PROTECTED]

Mississippi Welders Supply Co.

Phone: 507-454-5231

Fax:  507-454-8104

 

The side with the simplest uniforms wins. -- 59th Law of Combat

Reply via email to