Sure. The entry is in maintenance (first time) until 8pm. The first cycle after 8pm, it's active and executed, and the alert for it too (set to maintenance until 8pm).
Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark Bradshaw Sent: Monday, February 05, 2007 6:56 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse Would that still work if there isn’t a cycle executing at 8:00 exactly? From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Monday, February 05, 2007 10:46 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse There is a way to do this with 2 entries. (if you want the check to be done twice per day). Why not have the entry active all the time (schedule point of view) and then have an alert "command to execute"-"internal Servers Alive command"-"set entry to maintenance" (give the UID of the entry) until "8:00pm" That way it will get active again at 8:00pm and do one check, and be set to maintenance, next time it's after 8pm, it will be active for one cycle. And do the same for 8:00am. Then set both entries to maintenance until there normal checking time. Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Weigold, Greg Sent: Monday, February 05, 2007 4:26 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse One of the "issues" I have is trying to get a check to run once or twice a day, at fairly specific times... IE: I want to check for an SSL certificate's validity only once a day, at 8am (or there abouts)... I can narrow down things to run during the 8-8:15 block, but the check may run several times during that timeframe and generate more than the single error (or informational) message I want... I have the check set to run 1 out of 5 cycles, but depending on how long the full cycle takes.... Well, you get the picture. I'd love to be able to say "Do this check once a day, at 8am or the first cycle after 8am" or something like that... Thanks! Greg -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Monday, February 05, 2007 10:01 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse looking at it, it does not seem to be the type of schedule we're using. With the CRON schedule you can say that it has to run on a specific day/hour/minute, while what we do is run "all the time" except... Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Monday, February 05, 2007 2:41 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse Here's a good help file for vixie cron (ignore the bits that deal with their specific example about the variables). It covers the method/layout pretty well (at least as well as I understand it :-) ) and should cover all the uses you'd need. http://www.unixgeeks.org/security/newbie/unix/cron-1.html (http://www.unixgeeks.org/security/newbie/unix/cron-1.html) Michael D. Shook Systems Analyst - Data Integration Saddle Creek Corporation [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) 863 668 4477 (work) 863 665 1261 (fax) www.saddlecrk.com (http://www.saddlecrk.com/) -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Monday, February 05, 2007 8:26 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse No I'm not aware of that format. Can you give some examples/tips/hints/...? Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Monday, February 05, 2007 2:11 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse Are you familiar with how cron jobs schedule on a *nix server? That's probably the most concise 'readable' schedule description. Plus, it's only a single element per each alert. We use that format in other production software, so it would work well for us. Michael D. Shook Systems Analyst - Data Integration Saddle Creek Corporation [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) 863 668 4477 (work) 863 665 1261 (fax) www.saddlecrk.com (http://www.saddlecrk.com/) -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Sunday, February 04, 2007 1:56 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse About the schedule (as that seems to be one of the things you "need"), how do you see that within an XML file? Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Friday, February 02, 2007 10:11 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse Thanks, this will really look good for the managers. You rock!!! Michael D. Shook Systems Analyst - Data Integration Saddle Creek Corporation [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) 863 668 4477 (work) 863 665 1261 (fax) www.saddlecrk.com (http://www.saddlecrk.com/) -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Friday, February 02, 2007 3:46 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse For the export? I hope even before that :-) (that is before v7) Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Friday, February 02, 2007 9:31 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse YEAH!!!!!!!!!!!!! ummmmm, do you have a version eta? Maybe, dare I say, (dare!, dare!) version 7? Michael D. Shook Systems Analyst - Data Integration Saddle Creek Corporation [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) 863 668 4477 (work) 863 665 1261 (fax) www.saddlecrk.com (http://www.saddlecrk.com/) -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Friday, February 02, 2007 3:16 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse XML as output/export is an option. As input it's not (yet). Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Vogl, Tom Sent: Friday, February 02, 2007 8:01 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse Can I throw in my $.02 and ask for the config file to moved to an XML format - which will make it easier to parse/edit with external tools.... -Tom -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Friday, February 02, 2007 7:56 AM To: Servers Alive Discussion List Subject: [SA-list] Feature request, was: Changing alert recipients en masse Can I request a way to print out the alerts that each check have? Or better yet export a .csv with the alert data? I'd love: SAID UID Alert Recipients Alert Conditions Alert Schedule I have been asked repeatedly for this information so the managers of the teams can review it. Please, Please? Michael D. Shook Systems Analyst - Data Integration Saddle Creek Corporation [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) 863 668 4477 (work) 863 665 1261 (fax) www.saddlecrk.com (http://www.saddlecrk.com/) -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Friday, February 02, 2007 1:36 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Changing alert recipients en masse There is no option/feature to add alerts "en masse". Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Wuichner, Eric Sent: Thursday, February 01, 2007 11:06 PM To: Servers Alive Discussion List Subject: [SA-list] Changing alert recipients en masse Thanks to all for the help. The tool is doing some good things for us. I have about 450 devices doing ping checks only now every two minutes. What's the best way to set the same alert recipient for multiple devices at the same time? We want to make sure the right people get alerted for only the devices they support. Thanks again for your help, Eric To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. -------------------------------------- The information contained in this message is intended only for the use of the addressee. If the reader of this message is not the intended recipient or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of the message is strictly prohibited. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. -------------------------------------- The information contained in this message is intended only for the use of the addressee. If the reader of this message is not the intended recipient or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of the message is strictly prohibited. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. -------------------------------------- The information contained in this message is intended only for the use of the addressee. If the reader of this message is not the intended recipient or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of the message is strictly prohibited. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. -------------------------------------- The information contained in this message is intended only for the use of the addressee. If the reader of this message is not the intended recipient or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of the message is strictly prohibited. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. -------------------------------------- The information contained in this message is intended only for the use of the addressee. If the reader of this message is not the intended recipient or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of the message is strictly prohibited. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
